Skip to main content
Glama

update_creative

Modify the name and URL tags of an existing ad creative, as only these fields can be updated after creation.

Instructions

Update an existing ad creative. Only name and url_tags can be modified after creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
creative_idYesCreative ID to update
nameNoNew creative name
url_tagsNoNew URL tags

Implementation Reference

  • Registration of the 'update_creative' MCP tool via server.tool(), including its schema (creative_id required, name and url_tags optional) and handler function.
    // ─── update_creative ───────────────────────────────────────
    server.tool(
      "update_creative",
      "Update an existing ad creative. Only name and url_tags can be modified after creation.",
      {
        creative_id: z.string().describe("Creative ID to update"),
        name: z.string().optional().describe("New creative name"),
        url_tags: z.string().optional().describe("New URL tags"),
      },
      async ({ creative_id, name, url_tags }) => {
        try {
          const params: Record<string, unknown> = {};
          if (name) params.name = name;
          if (url_tags) params.url_tags = url_tags;
          const { data, rateLimit } = await client.post(`/${creative_id}`, params);
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Handler function for update_creative. Takes creative_id, name, url_tags; builds params and sends POST request to /{creative_id} via the AdsClient. Returns JSON result or error.
    async ({ creative_id, name, url_tags }) => {
      try {
        const params: Record<string, unknown> = {};
        if (name) params.name = name;
        if (url_tags) params.url_tags = url_tags;
        const { data, rateLimit } = await client.post(`/${creative_id}`, params);
        return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
      } catch (error) {
        return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
      }
    }
  • Input schema for update_creative using Zod: creative_id (string, required), name (string, optional), url_tags (string, optional). Description states only name and url_tags can be modified after creation.
    {
      creative_id: z.string().describe("Creative ID to update"),
      name: z.string().optional().describe("New creative name"),
      url_tags: z.string().optional().describe("New URL tags"),
    },
  • The AdsClient.post() helper method used by the update_creative handler to send the POST request.
    async post(
      path: string,
      params?: Record<string, unknown>
    ): Promise<ClientResponse> {
      return this.request("POST", path, params);
  • src/index.ts:53-53 (registration)
    Registration call in index.ts that wires up registerCreativeTools (which includes update_creative) during server initialization.
    registerCreativeTools(server, client);
Behavior4/5

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

With no annotations, the description carries the full burden. It correctly identifies the tool as an update (mutation) and specifies the modifiable fields. It does not mention side effects or auth, but for a straightforward update, this is adequate.

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?

Two sentences, no wasted words, and the core action is stated first. Highly efficient.

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

Completeness4/5

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

For a simple update tool with 3 parameters and no output schema, the description is sufficiently complete. It tells the agent what the tool does and what is modifiable. Lacks info on return value or error handling, but these are not critical given the tool's simplicity.

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 coverage is 100%, so parameters are already well-described. The description adds the constraint that only 'name' and 'url_tags' can be updated, which is helpful but doesn't add deeper semantics beyond what the schema provides.

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 'Update an existing ad creative', using a specific verb and resource, and distinguishes itself from create_creative by noting that only certain fields are modifiable after creation.

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

Usage Guidelines4/5

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

The description explicitly states that only 'name' and 'url_tags' can be modified after creation, providing clear context for when to use this tool and implicitly when not to (e.g., for fields not listed). However, it does not explicitly mention alternatives.

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/mikusnuz/meta-ads-mcp'

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