Skip to main content
Glama

Update payout recipient

zora_update_payout_recipient

Change the payout recipient address for creator earnings on Zora Coins. Requires owner wallet authorization to update the address receiving earnings.

Instructions

Change the payout recipient address (creator earnings). Requires owner wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYes
newPayoutRecipientYes

Implementation Reference

  • The handler function validates wallet presence, invokes CoinsSDK.updatePayoutRecipient to perform the update on the blockchain, and formats the transaction result as MCP content.
    async ({ coin, newPayoutRecipient }) => {
      ensureWallet();
      const result = await CoinsSDK.updatePayoutRecipient(
        { coin: coin as any, newPayoutRecipient: newPayoutRecipient as any },
        walletClient!,
        publicClient
      );
      return { content: [{ type: "text", text: json(result) }] };
    }
  • Zod input schema requiring 'coin' (contract address) and 'newPayoutRecipient' (new recipient address) as non-empty strings.
      coin: z.string().min(1),
      newPayoutRecipient: z.string().min(1),
    },
  • src/index.ts:410-430 (registration)
    Registers the tool with McpServer, providing name, metadata (title, description, inputSchema), and the execution handler.
    server.registerTool(
      "zora_update_payout_recipient",
      {
        title: "Update payout recipient",
        description:
          "Change the payout recipient address (creator earnings). Requires owner wallet.",
        inputSchema: {
          coin: z.string().min(1),
          newPayoutRecipient: z.string().min(1),
        },
      },
      async ({ coin, newPayoutRecipient }) => {
        ensureWallet();
        const result = await CoinsSDK.updatePayoutRecipient(
          { coin: coin as any, newPayoutRecipient: newPayoutRecipient as any },
          walletClient!,
          publicClient
        );
        return { content: [{ type: "text", text: json(result) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions a requirement ('Requires owner wallet') which adds useful context about permissions, but it doesn't cover other critical aspects like whether this is a destructive/mutative operation (implied by 'Change'), rate limits, error conditions, or what happens to existing payouts. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 extremely concise with two sentences that are front-loaded: the first states the purpose, and the second adds a key constraint. Every word earns its place with no redundancy or fluff, making it efficient and easy to parse.

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's complexity (a mutation operation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It covers the basic purpose and a permission requirement but misses details on parameter usage, behavioral traits (e.g., idempotency, side effects), and expected outcomes. For a tool that modifies financial payouts, this is inadequate.

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 for undocumented parameters. It mentions 'payout recipient address' which relates to 'newPayoutRecipient', but doesn't explain 'coin' at all (e.g., what coin identifier to use). The description adds minimal meaning beyond the schema, failing to fully address the coverage gap for both parameters.

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 ('Change') and resource ('payout recipient address'), specifying it's for 'creator earnings'. It distinguishes from siblings like 'zora_update_coin_uri' by focusing on payout addresses rather than coin metadata. However, it doesn't explicitly differentiate from all siblings (e.g., 'zora_trade_coin' is also a write operation).

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 provides some context with 'Requires owner wallet', implying usage is restricted to owners. However, it doesn't specify when to use this versus alternatives (e.g., no guidance on whether this is for initial setup or updates, or if there are other tools for managing payouts). The context is implied but lacks explicit alternatives or exclusions.

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