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

konquest-meta-ads-mcp

by brandu-mos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_demographics

Find demographic segments for ad targeting. Filter by keyword such as homeowner or education, or retrieve all available options.

Instructions

Search or list demographic targeting options.

Returns demographic categories: life events, education, work, financial, relationship, home ownership, parental status, etc.

If query is provided, filters by keyword. Otherwise returns all demographics.

Args: query: Optional search term (e.g., 'homeowner', 'new job', 'university'). limit: Max results (default 30).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description bears full burden. It explains the filtering and listing behavior, but does not mention side effects, authorization needs, or rate limits. However, as a read-only search tool, the description is sufficient.

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?

Description is brief: three sentences plus bulleted args. Purpose is front-loaded. No redundant or unnecessary information.

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 search tool with two parameters and no output schema, the description covers all necessary behavioral details. It explains when filtering occurs and what kind of data is returned.

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

Parameters5/5

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

Schema coverage is 0%, yet description clearly explains both parameters: query (optional search term with examples) and limit (default 30). Adds meaning beyond schema's type and default.

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?

Description uses specific verb 'Search or list' and clearly identifies the resource as 'demographic targeting options'. Lists example categories (life events, education, etc.), distinguishing it from sibling tools like search_interests or search_behaviors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States behavior with and without query: 'If query is provided, filters by keyword. Otherwise returns all demographics.' Implicitly suggests usage for demographic targeting, but does not explicitly exclude other scenarios or compare to sibling tools.

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