Miro Developer App ACTION
Update Shape
Updates content of an existing shape on a Miro board. See the docs.
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Miro Developer App account once, then configure and run Update Shape from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "miro_custom_app-update-shape",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
miro_custom_app: { authProvisionId: "apn_xxxxxxx" },
teamId: "Team ID",
boardId: "Board ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "miro_custom_app-update-shape",
"configured_props": {
"miro_custom_app": { "authProvisionId": "apn_xxxxxxx" },
"teamId": "Team ID",
"boardId": "Board ID"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "miro_custom_app",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "miro_custom_app-update-shape",
arguments: {
teamId: "Team ID",
boardId: "Board ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
teamId Team ID | string | The team_id for which you want to retrieve the list of boards. Optional |
boardId Board ID | string | The ID of a board Required Dynamic |
itemId Item ID | string | The ID of an item (Shape) Required Dynamic |
content Content | string | The text you want to display on the shape. Optional |
shape Shape Type | string | Defines the geometric shape of the item when it is rendered on the board. Optional |
x X Position | integer | X-axis coordinate of the location of the item on the board. By default, all items have absolute positioning to the board, not the current viewport. The center point of the board has x: 0 and y: 0 coordinates. Required |
y Y Position | integer | Y-axis coordinate of the location of the item on the board. By default, all items have absolute positioning to the board, not the current viewport. The center point of the board has x: 0 and y: 0 coordinates. Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- miro_custom_app-update-shape
- Version
- 0.0.3
- App
- Miro Developer App
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗