Skip to main content
Glama

ADS Beast

campaign_search

Read-only

Campaigns filtered by client, platform, status or a substring of the name.

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": "campaign_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo50 by default, 200 at most.
statusNoOnly records in this status.
platformNogoogle, meta, tiktok, linkedin or microsoft.
client_idNo
name_filterNoCase-insensitive substring of the campaign name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the filter list, and its use of 'or' leaves unclear whether filters combine with AND or OR, which matters for interpreting results.

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?

It is a single compact sentence with no wasted wording. It is arguably too terse for a five-parameter tool, but the phrasing is front-loaded and efficient.

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?

For a search tool with five optional parameters and no output schema, the description does not explain how filters combine, whether results are paginated beyond the limit, or how results are ordered. The annotations cover safety, but the remaining behavioral gaps are material.

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?

Schema coverage is 80%, with descriptions for limit, status, platform, and name_filter; only client_id is undocumented. The description mirrors those parameter names and adds little beyond the schema, so the baseline 3 is appropriate.

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 identifies the resource (campaigns) and the filtering dimensions (client, platform, status, name substring), so an agent can tell this is a filtered campaign search. It stops short of explicitly distinguishing it from siblings like get_campaign or campaign_analyze.

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?

It implies the tool is for searching campaigns with filters, but gives no explicit when-to-use guidance, no prerequisites, and no alternatives or exclusions relative to the many sibling 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.