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

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_adset_targeting_sentence

Converts Meta Ads ad set targeting specifications into readable sentences for easy understanding of audience criteria.

Instructions

Get human-readable targeting description for an ad set. Converts targeting spec into readable sentences.

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": {
      "adset_id": "<adset_id>"
    },
    "name": "get_adset_targeting_sentence"
  }
}

Input Schema

NameRequiredDescriptionDefault
adset_idYesAd set ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It indicates the tool converts a targeting spec into readable sentences, but it does not disclose whether it fetches the ad set, returns plain text, or has any side effects. The behavior is somewhat transparent but lacks safety and boundary details.

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 two concise sentences that are front-loaded with the action and resource. The second sentence clarifies the first without excessive redundancy, making it efficiently worded.

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

Completeness4/5

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

Given the tool's simplicity (one parameter, no output schema) and the self-explanatory nature of the output (a human-readable sentence), the description is sufficiently complete. It does not explain return structure but that is not critical here.

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 schema describes the single parameter adset_id with a simple 'Ad set ID' description, giving 100% coverage. The tool description adds no extra meaning beyond the schema, so the baseline of 3 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 tool gets a human-readable targeting description for an ad set and converts the targeting spec into readable sentences. This distinguishes it from sibling tools by its unique function of generating descriptive text rather than raw data.

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 about when to use this tool compared to alternatives. It does not mention whether to prefer this over get_adset or search_targeting, nor does it specify any prerequisites or contexts where it is not appropriate.

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