Skip to main content
Glama

Get Ad Details

meta_get_ad
Read-onlyIdempotent

Retrieve detailed information about a specific ad using its ID. Access performance metrics and creative details.

Instructions

Gets detailed information about a specific ad.

Args:

  • ad_id (string): Ad ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYes
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior3/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description adds no extra behavioral context. It does not contradict annotations, but also does not disclose additional traits like authentication or data freshness.

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

Conciseness3/5

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

The description is very short but lacks structured front-loading of key information. It could be slightly more organized, but it is not verbose.

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

Completeness2/5

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

Given the tool has only two parameters and no output schema, the description should clarify what 'detailed information' includes or distinguish it from similar tools. It does not, leaving the description incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description only lists ad_id with a trivial explanation 'Ad ID,' adding no value beyond the parameter name. The response_format parameter is omitted entirely from the description, despite the schema having a useful enum description. Schema description coverage is 50%, and the description does not compensate for the uncovered parameter.

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 'Gets detailed information about a specific ad,' with a specific verb and resource. Among sibling tools like meta_get_ad_creative or meta_get_ad_insights, it uniquely identifies the purpose of retrieving ad details.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it or which sibling tools might be more appropriate for specific needs.

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/oliverames/meta-mcp-server'

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