Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_experiment_results

Retrieve results and cells from a Facebook ad experiment (ad study) using its ID. Specify optional fields to customize the data returned.

Instructions

Get results/cells of an experiment (ad study).

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": {
      "experiment_id": "<experiment_id>"
    },
    "name": "get_experiment_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields to return
experiment_idYesExperiment (ad study) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. It only says 'Get results/cells' without detailing return format, pagination, field filtering behavior, or any side effects. The safety profile is only implied by the verb 'get', which is insufficient for full transparency.

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, efficient sentence with no filler. It is front-loaded with the verb and resource. However, it is extremely terse and could profitably include a note about the 'fields' parameter or return format without becoming verbose.

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?

The tool has low complexity (2 params, no nested objects) but no output schema, so the description must explain return values. 'Results/cells' vaguely indicates what is returned but lacks detail on structure or filtering. The description is minimally adequate for a simple getter.

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?

The input schema has full descriptive coverage: experiment_id is 'Experiment (ad study) ID' and fields is 'Comma-separated fields to return'. The description adds no additional meaning beyond this schema, so the baseline score applies.

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 the verb 'Get' and the resource 'results/cells of an experiment (ad study)'. This distinguishes it from sibling tools like get_experiment, which likely fetches experiment metadata, making the purpose unambiguous.

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 when to use the tool (when you need experiment results/cells) but provides no explicit guidance on alternatives or exclusions. It does not mention when to use get_experiment instead, leaving usage context to be inferred from the name.

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

Deploy Server

Other Tools