Skip to main content
Glama

ADS Beast

meta_ads_interest_search

Read-only

Targeting interests matching a keyword, with id, name, audience size and topic.

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": {
      "client_id": "<client_id>",
      "query": "<query>"
    },
    "name": "meta_ads_interest_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records.
queryYesKeyword, for example fitness or real estate.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this as a read-only, open-world, non-destructive search. The description adds value by naming returned fields, but does not discuss pagination, rate limits, result relevance, or how the default limit of 15 affects behavior.

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?

The description is a single front-loaded sentence with no wasted words. It efficiently communicates the operation and key output fields.

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 no output schema, the description helpfully names several returned fields. However, it leaves important context gaps around client_id, result limiting, and when this search should be used relative to sibling tools.

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 schema documents query and limit, but leaves client_id undescribed. The description only restates the keyword-matching idea already present in the schema and adds no meaning about client_id or how limit interacts with returned results.

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?

The description clearly identifies the resource as Meta Ads targeting interests and the operation as matching by keyword. It also previews returned fields (id, name, audience size, topic), though it does not explicitly differentiate this search from sibling tools.

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 implies usage for interest targeting, but gives no explicit guidance on when to use this tool versus alternatives. It also does not state prerequisites such as needing a client context or when this search is preferable to broader audience or campaign tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.