Skip to main content
Glama
citesurf

Citesurf MCP

by citesurf

update_brand

Idempotent

Modify brand metadata for AI platform monitoring, including classification, description, category, or search prompts to track visibility.

Instructions

Update brand metadata: type, category, description, or monitoring prompts. All fields optional, only pass what you want to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandIdYesThe brand ID to update
typeNoBrand classification
categoryNoBusiness category (e.g. 'AI Resume Builder')
descriptionNoBrand description (2 to 3 sentences)
promptsNoExactly 3 search prompts to monitor

Implementation Reference

  • The handler function that executes the 'update_brand' tool logic.
    async ({ brandId, ...data }) => {
      try {
        const body = Object.fromEntries(
          Object.entries(data).filter(([, v]) => v !== undefined)
        );
        const result = await client.patch<ApiResponse<BrandUpdateResult>>(
          `/brands/${encId(brandId)}`,
          body
        );
        return jsonText(result.data);
      } catch (err) {
        return errorText(err);
      }
    }
  • The input schema definition for the 'update_brand' tool.
    inputSchema: z.object({
      brandId: z.string().describe("The brand ID to update"),
      type: z
        .enum(["PERSON", "PRODUCT", "COMPANY", "SHOP"])
        .optional()
        .describe("Brand classification"),
      category: z
        .string()
        .max(100)
        .optional()
        .describe("Business category (e.g. 'AI Resume Builder')"),
      description: z
        .string()
        .max(500)
        .optional()
        .describe("Brand description (2 to 3 sentences)"),
      prompts: z
        .array(z.string().min(5).max(200))
        .length(3)
        .optional()
        .describe("Exactly 3 search prompts to monitor"),
    }),
  • Registration of the 'update_brand' tool with the MCP server.
    server.registerTool(
      "update_brand",
      {
        description:
          "Update brand metadata: type, category, description, or monitoring prompts. All fields optional, only pass what you want to change.",
        annotations: { idempotentHint: true },
        inputSchema: z.object({
          brandId: z.string().describe("The brand ID to update"),
          type: z
            .enum(["PERSON", "PRODUCT", "COMPANY", "SHOP"])
            .optional()
            .describe("Brand classification"),
          category: z
            .string()
            .max(100)
            .optional()
            .describe("Business category (e.g. 'AI Resume Builder')"),
          description: z
            .string()
            .max(500)
            .optional()
            .describe("Brand description (2 to 3 sentences)"),
          prompts: z
            .array(z.string().min(5).max(200))
            .length(3)
            .optional()
            .describe("Exactly 3 search prompts to monitor"),
        }),
      },
      async ({ brandId, ...data }) => {
        try {
          const body = Object.fromEntries(
            Object.entries(data).filter(([, v]) => v !== undefined)
          );
          const result = await client.patch<ApiResponse<BrandUpdateResult>>(
            `/brands/${encId(brandId)}`,
            body
          );
          return jsonText(result.data);
        } catch (err) {
          return errorText(err);
        }
      }
    );
Behavior3/5

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

Annotations provide idempotentHint=true, indicating safe retries. The description adds that fields are optional and partial updates are supported, which is useful behavioral context beyond annotations. However, it doesn't cover other aspects like permissions, rate limits, or error handling.

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 that front-loads the purpose and key usage note. Every word earns its place with no redundancy or fluff, making it easy to parse quickly.

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 an update tool with idempotent annotations and full schema coverage, the description is adequate but minimal. It lacks output details (no output schema provided) and doesn't address potential side effects or dependencies, leaving some gaps in context.

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?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds that 'All fields optional, only pass what you want to change', clarifying partial update semantics, but doesn't provide additional meaning beyond the schema's detailed descriptions.

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 verb ('Update') and resource ('brand metadata'), specifying which fields can be updated (type, category, description, prompts). However, it doesn't explicitly differentiate from sibling tools like 'create_brand' or 'update_insight', though the focus on updating existing brands is implied.

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 modifying existing brand metadata, with 'All fields optional, only pass what you want to change' suggesting partial updates. No explicit guidance on when to use this vs. alternatives like 'create_brand' or 'update_insight' is provided, leaving it to context.

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/citesurf/mcp'

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