Skip to main content
Glama
Upload-Post

Upload-Post

Official

List Pinterest boards

get_pinterest_boards
Read-only

Returns the Pinterest boards for a given profile, enabling board selection for pin scheduling or analysis.

Instructions

Pinterest boards available to a profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'available to a profile', clarifying scope but does not disclose additional behavioral traits like pagination or ordering. Given annotation coverage, this is adequate but not enriched.

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

Conciseness4/5

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

Description is a single concise sentence with no repetition. It earns its place but could be slightly more informative without sacrificing conciseness.

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

Completeness2/5

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

Even with annotations and an output schema, the description lacks explanation of how the profile parameter works, what happens when omitted, and what the returned boards represent. This leaves the agent guessing.

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

Parameters1/5

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

The sole parameter 'profile' has 0% schema description coverage and the description does not explain its meaning, required values, or default behavior. The agent cannot determine what to pass for this parameter.

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

Purpose4/5

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

The title 'List Pinterest boards' and description 'Pinterest boards available to a profile' clearly indicate the tool lists boards for a given profile. It distinguishes well from sibling tools focused on scheduling, media, users, etc.

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

Usage Guidelines2/5

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

No usage context or alternative recommendations are provided. The description does not indicate when to use this tool versus other listing tools like get_facebook_pages or get_linkedin_pages.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Upload-Post/upload-post-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server