Skip to main content
Glama
markswendsen-code

@striderlabs/mcp-pinterest

follow_user

Follow a Pinterest user by entering their username. Connect with creators and stay updated on their pins and boards.

Instructions

Follow a Pinterest user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesUsername to follow
Behavior1/5

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

No annotations are provided, so the description carries the full burden of disclosure. It fails to mention any side effects, permission requirements, rate limits, or whether the action is reversible. For a mutation operation, this is a significant gap.

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?

The description is a single, concise sentence with no redundancy. It is appropriately sized for a simple tool, though it could have included a bit more context without unnecessary length.

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?

With no annotations and no output schema, the description should explain behavioral expectations and prerequisites. It only states the action, omitting important context for a mutation tool, such as whether the user must be logged in or what happens if already following.

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?

The schema already describes the single parameter 'username' with 'Username to follow', achieving 100% coverage. The description adds no extra semantic value beyond what the schema provides, hence the baseline 3.

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 'Follow a Pinterest user' clearly states the specific action (follow) and the resource (a Pinterest user). It is unambiguous and distinct from all sibling tools, none of which involve following.

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?

There is no guidance on when to use this tool vs alternatives. The description only states the action, leaving the agent to infer the appropriate context from the tool name.

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/markswendsen-code/mcp-pinterest'

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