pinbridge

Create board

create_board

Create a new board on a connected Pinterest account.

    Use when no existing board from list_boards fits; check list_boards
    first, since Pinterest rejects duplicate names. Not needed for a
    one-off pin: publish to an existing board.

    Returns the board with id (use as board_id), name, description,
    privacy. Fails with forbidden (sandbox_board_limit) when a sandbox
    project hits its board cap, and token_expired / scope_missing when the
    Pinterest connection needs a reconnect (scope_missing with
    missing_scopes ["boards:write_secret"] for SECRET on an account connected
    before secret boards were supported).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Board name, unique within the account, <= 180 characters.
`privacy`	No	"PUBLIC" (default) or "SECRET". SECRET needs the account to be connected with Pinterest's boards:write_secret permission; older connections fail with scope_missing until reconnected.
`account_id`	Yes	UUID of a connected Pinterest account, from list_pinterest_accounts.
`description`	No	Board description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / privacy / description

Previous value: -"\"PUBLIC\" (default) or \"SECRET\"."New value: +"\"PUBLIC\" (default) or \"SECRET\". SECRET needs the account to be connected with Pinterest's boards:write_secret permission; older connections fail with scope_missing until reconnected."

Changed4 schema fields changedSep 24, 2026
- addedInput schema / properties / account_id / description
```
Added value: +"UUID of a connected Pinterest account, from list_pinterest_accounts."
```
- addedInput schema / properties / description / description
```
Added value: +"Board description."
```
- addedInput schema / properties / name / description
```
Added value: +"Board name, unique within the account, <= 180 characters."
```
- addedInput schema / properties / privacy / description
```
Added value: +"\"PUBLIC\" (default) or \"SECRET\"."
```

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / privacy / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "PUBLIC",
+      "SECRET"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

First observedSep 23, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes well beyond annotations by disclosing the return shape (board with id, name, description, privacy), and enumerating specific failure modes: forbidden (sandbox_board_limit), token_expired, and scope_missing with missing_scopes ["boards:write_secret"]. This gives the agent actionable context for handling errors, which the annotations (readOnlyHint=false, idempotentHint=false) do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then organized into usage guidance and failure modes. Every sentence is informative: the duplicate-name warning, the one-off pin alternative, the return format, and the sandbox/auth errors all earn their place. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the description's return-format disclosure is essential and fully covers what an agent needs. It also addresses the two main external failure categories (sandbox caps and auth/scope issues), making the tool self-sufficient for correct invocation and error handling. Sibling context is handled via the explicit list_boards reference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter already has a clear meaning in the schema. The description adds no new parameter-level semantics; its mention of SECRET permissions and missing_scopes echoes the privacy parameter schema rather than extending it. Per the calibration rule, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-resource pair: 'Create a new board on a connected Pinterest account.' It clearly distinguishes this from siblings like update_board and delete_board by specifying 'new board', and the follow-up line about returning the board with id further anchors what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'Use when no existing board from list_boards fits; check list_boards first, since Pinterest rejects duplicate names.' It also gives a when-not-to-use: 'Not needed for a one-off pin: publish to an existing board.' This names the alternative tool (list_boards) and the condition that selects it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pinbridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?