pinterest_board_pins_listList public pins on a Pinterest board by URL. Returns a list (use cursor when paginated).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Link to the Pinterest board. | |
| trim | No | When true, returns a smaller response with fewer fields. | |
| cursor | No | Opaque pagination cursor returned by a previous response. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, establishing a safe read operation. The description adds that it returns a list and mentions cursor pagination, but this is partially redundant with the schema's cursor field description. No additional behavioral context like rate limits or response format is provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no fluff; purpose is front-loaded and the pagination hint is placed second. Every word earns its place, and the structure is easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with full schema coverage and safety annotations, the description covers the essentials: what it lists, how it takes input, and pagination behavior. It lacks details on return fields or trim behavior, but these are not critical for basic invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all parameters (url, trim, cursor) are already documented. The description's mention of cursor pagination adds minimal value beyond the schema. No new parameter details are introduced.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Explicitly states it lists public pins on a Pinterest board by URL, clearly distinguishing it from siblings like pinterest_pin_get (single pin) and pinterest_search_pins_list (search). The verb 'list' and the resource 'public pins on a Pinterest board' are precise and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides implicit usage context through 'by URL' and 'public pins', but does not explicitly name alternatives or exclusion conditions. No mention of when to prefer this over pinterest_profile_boards_list or pinterest_search_pins_list, leaving the agent to infer from naming conventions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.
All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).
The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.
The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.