Skip to main content
Glama

Get profile-created coins

zora_get_profile_coins

Retrieve coins created by a profile on Zora Coins to analyze creator activity and explore their tokenized assets.

Instructions

List coins created by a profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
countNo
afterNo
chainIdsNo
platformReferrerAddressNo

Implementation Reference

  • src/index.ts:228-246 (registration)
    Registers the 'zora_get_profile_coins' MCP tool, defining its schema and thin handler wrapper around CoinsSDK.getProfileCoins
    server.registerTool(
      "zora_get_profile_coins",
      {
        title: "Get profile-created coins",
        description: "List coins created by a profile.",
        inputSchema: {
          identifier: z.string(),
          count: z.number().int().min(1).max(100).optional(),
          after: z.string().optional(),
          chainIds: z.array(z.number()).optional(),
          platformReferrerAddress: z.array(z.string()).optional(),
        },
      },
      async (args) => {
        // @ts-expect-error - TypeScript can't resolve barrel exports properly
        const resp = await CoinsSDK.getProfileCoins(args);
        return { content: [{ type: "text", text: json(resp) }] };
      }
    );
  • Handler function executes the tool logic by calling CoinsSDK.getProfileCoins with input args and formats response as MCP content
    async (args) => {
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      const resp = await CoinsSDK.getProfileCoins(args);
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Input schema using Zod for validating tool parameters: identifier (required), optional pagination (count, after), chainIds, and platformReferrerAddress
    {
      title: "Get profile-created coins",
      description: "List coins created by a profile.",
      inputSchema: {
        identifier: z.string(),
        count: z.number().int().min(1).max(100).optional(),
        after: z.string().optional(),
        chainIds: z.array(z.number()).optional(),
        platformReferrerAddress: z.array(z.string()).optional(),
      },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('List'), implying it's likely safe and non-destructive, but doesn't disclose any behavioral traits such as pagination (hinted by 'after' parameter), rate limits, authentication needs, or what the output looks like. This leaves significant gaps for an agent to understand how to interact with it effectively.

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, clear sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

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?

Given the tool has 5 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't address parameter meanings, behavioral aspects, or output format, leaving the agent with insufficient context to use the tool correctly beyond a basic understanding of its purpose.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but doesn't mention any parameters. It doesn't explain what 'identifier' refers to (e.g., profile ID or address), what 'count' limits, the purpose of 'after' (likely pagination cursor), 'chainIds' filtering, or 'platformReferrerAddress'. This leaves all 5 parameters undocumented beyond their schema types.

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 description clearly states the action ('List') and resource ('coins created by a profile'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'zora_get_coins' or 'zora_get_coin', which might also list coins but with different scopes or filters.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'zora_get_coins' (likely general coin listing) and 'zora_get_coin' (likely single coin details), there's no indication of the specific context or prerequisites for using this profile-focused tool.

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/r4topunk/zora-coins-mcp-server'

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