Skip to main content
Glama

get_creative

Retrieve details of a specific ad creative by its ID. Use this to access fields for ad creative analysis and management.

Instructions

Get details of a specific ad creative by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
creative_idYesCreative ID
fieldsNoComma-separated fields to return

Implementation Reference

  • The handler function for the 'get_creative' tool. Calls the Meta Ads API with the creative_id to get details of a specific ad creative.
    server.tool(
      "get_creative",
      "Get details of a specific ad creative by ID.",
      {
        creative_id: z.string().describe("Creative ID"),
        fields: z.string().optional().describe("Comma-separated fields to return"),
      },
      async ({ creative_id, fields }) => {
        try {
          const params: Record<string, unknown> = {};
          if (fields) params.fields = fields;
          const { data, rateLimit } = await client.get(`/${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 definition for 'get_creative': requires creative_id (string), optionally accepts fields (string).
    {
      creative_id: z.string().describe("Creative ID"),
      fields: z.string().optional().describe("Comma-separated fields to return"),
    },
  • The registerCreativeTools function that registers the 'get_creative' tool (and siblings) on the MCP server.
    export function registerCreativeTools(server: McpServer, client: AdsClient): void {
  • src/index.ts:53-53 (registration)
    Where registerCreativeTools is called to register the 'get_creative' tool on the main MCP server.
    registerCreativeTools(server, client);
Behavior2/5

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

No annotations exist, and the description only states 'Get details', which implies a read operation but adds no behavioral detail (e.g., rate limits, permissions, or what 'details' entails). The description does not go beyond what the tool name suggests.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no unnecessary words. It is appropriately front-loaded with the verb and resource, though it could be slightly expanded for completeness without losing 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?

Given the low complexity (2 parameters, no output schema) and good sibling differentiation, the description is adequate but minimal. It states the tool's purpose but omits any notes on return format, available fields, or potential errors, leaving gaps for an agent.

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?

With 100% schema coverage, the schema already documents both parameters ('creative_id' and 'fields'). The description adds no additional meaning or constraints beyond what the schema provides, meeting the baseline of 3.

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 uses a specific verb ('Get') and resource ('details of a specific ad creative by ID'), clearly distinguishing it from sibling tools like list_creatives or create_creative.

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 (e.g., list_creatives for multiple creatives, update_creative for modifications). The agent must infer usage solely from the name.

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