ppc_campaign_create_guideThe verified contract for creating campaigns via stage_campaign_create: per-format required fields, goals, landing-page rules, asset sourcing, safety model, and post-create lifecycle. CALL THIS FIRST whenever the user asks to create an SB campaign.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only and non-destructive, and the description aligns with that. It adds useful behavioral context by describing its role as a pre-creation contract and listing lifecycle/safety topics, beyond what annotations convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences deliver strong signal: the tool's role, content scope, and exact invocation trigger. The imperative call-to-action is front-loaded, and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only guide with no output schema, the description fully covers what the agent needs: what the tool is, what it contains, and when to call it. No important operational gap remains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is vacuously 100%, so parameter-level explanation is unnecessary. Baseline 4 applies; the description's content focus is appropriate for a guide tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly defines this as the verified contract/guide for creating campaigns via stage_campaign_create, enumerating the exact content areas it covers. It distinguishes itself from stage_campaign_create and other PPC tools by positioning itself as the prerequisite reference guide.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs the agent when to use it: 'CALL THIS FIRST whenever the user asks to create an SB campaign.' It also names the dependent operation (stage_campaign_create), making the workflow ordering unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.