Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

get

Read-onlyIdempotent

Retrieve a Meta campaign, ad set, ad, creative, or other object by ID, with optional Graph API fields.

Instructions

Get one campaign, ad set, ad, creative, or other object by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Meta object ID.
fieldsNoComma-separated Graph API fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds only that it accepts 'other object' types, which hints at breadth but does not state behavior on invalid IDs, access restrictions, or returned payload shape.

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?

A single front-loaded sentence with no filler and no redundant preamble. 'or other object' is slightly loose but earns its place by signaling broad object-type support.

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

Completeness5/5

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

For a simple two-parameter read tool with full schema coverage and annotations that carry the safety profile, this is sufficient. Nothing critical to calling it correctly is missing given the absence of an output schema.

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 both 'id' and 'fields' are already documented in the schema. The description reinforces that 'id' is a Meta object ID but says nothing about the 'fields' parameter or field-selection syntax, so it adds no meaning beyond the schema.

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?

Names a specific verb ('Get') and enumerates the resource types it returns (campaign, ad set, ad, creative, or other object) with a clear 'by ID' scope. This implicitly separates it from list/create/update/delete siblings, though it never names an alternative explicitly.

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 'by ID' scope implies usage: fetch a single known object rather than enumerate. However, there is no explicit statement of when to prefer this over 'list' or the insights sibling, and no note about prerequisites such as permissions or valid object IDs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.