Skip to main content
Glama

list_pinterest_boards

List Pinterest boards for a connected account by providing the account ID to retrieve board names and identifiers.

Instructions

List Pinterest boards for a connected Pinterest account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
socialMediaIdYesPinterest account ID (from list_accounts)

Implementation Reference

  • Registration of the 'list_pinterest_boards' tool via server.tool() with schema and handler.
    server.tool(
      'list_pinterest_boards',
      'List Pinterest boards for a connected Pinterest account',
      {
        socialMediaId: z
          .string()
          .uuid()
          .describe('Pinterest account ID (from list_accounts)'),
      },
      async (input) => {
        const data = await client.get<PinterestBoard[]>(
          `/social-media/${input.socialMediaId}/pinterest-boards`,
        );
    
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler function for list_pinterest_boards: calls GET /social-media/{socialMediaId}/pinterest-boards and returns results as JSON text.
    async (input) => {
      const data = await client.get<PinterestBoard[]>(
        `/social-media/${input.socialMediaId}/pinterest-boards`,
      );
    
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • Input schema for list_pinterest_boards: requires 'socialMediaId' (UUID) described as 'Pinterest account ID (from list_accounts)'.
    {
      socialMediaId: z
        .string()
        .uuid()
        .describe('Pinterest account ID (from list_accounts)'),
    },
  • PinterestBoard type definition with fields: id, boardId, name, description, imageUrl.
    export interface PinterestBoard {
      id: string;
      boardId: string;
      name: string;
      description: string | null;
      imageUrl: string | null;
    }
  • src/index.ts:18-19 (registration)
    The registerAccountTools function (which registers list_pinterest_boards) is called in the main entry point.
    registerAccountTools(server, client);
    registerFileTools(server, client);
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only status, rate limits, or authentication requirements. The description carries the full burden and fails to add such context.

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 a single, efficient sentence with no unnecessary words, achieving high conciseness.

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

Completeness3/5

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

For a simple list tool with one parameter and no output schema, the description is adequate but lacks details on return format, pagination, or any behavioral constraints that would help an agent use it correctly.

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 input schema has 100% coverage with a clear description for socialMediaId. The tool description adds no additional meaning beyond the schema, so baseline 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 clearly states the verb 'list' and resource 'Pinterest boards', and specifies 'for a connected Pinterest account', distinguishing it from sibling tools like list_posts or list_accounts.

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

Usage Guidelines3/5

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

The description implies usage for listing boards but provides no explicit guidance on when to use versus alternatives or prerequisites like having a connected account.

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/peturgeorgievv-factory/postfast-mcp'

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