Skip to main content
Glama

The Marketing Vault

Plan traffic

plan_traffic

Creates traffic strategy or channel setup and launch plans. Output is saved to the Library and uses one generation. Nothing is sent or published.

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": {
      "template": "<template>",
      "details": "<details>"
    },
    "name": "plan_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsYesWhat the user wants, including supplied source text, goals or constraints.
templateYestraffic-strategy: Plan traffic strategy, budget and timeline. channel-launch-blueprint: Plan setup and launch of a traffic channel.
offer_detailsNoOffer details for the selected template.
existing_assetsNoExisting assets for the selected template.
icp_descriptionNoIcp description for the selected template.
traffic_channelNoTraffic channel for the selected template.
business_contextNoBusiness context for the selected template.
budget_and_timelineNoBudget and timeline for the selected template.
business_profile_idNoBusiness profile id. Required when the account has multiple Businesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic safety flags; the description adds substantive context: output persists to the Library, consumes one generation (quota cost), and nothing is sent or published. That meaningfully extends what the agent knows beyond structured fields, though it omits permission or overwrite 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?

Three short sentences, action first, then persistence and quota, then the non-publishing guarantee. Every sentence carries distinct information with no padding.

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?

For a 9-parameter generation tool with full schema coverage and no output schema, the description covers effect, cost, and destination sufficiently. It could note that output lands in list_saved_outputs or how the two templates differ, but nothing critical to invocation is missing.

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 100% and each parameter already carries its own description, so the schema does the heavy lifting. The description adds no extra meaning about how details, template, or the optional context fields interact, so baseline 3 applies.

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?

Uses a specific verb+resource ('Creates traffic strategy or channel setup and launch plans') and covers both template variants. It is clear what the tool produces, though it doesn't explicitly contrast itself with planning siblings like plan_priorities_and_data or design_offer.

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

Usage Guidelines3/5

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

The two template names imply the two use cases, but the description never states when to pick traffic-strategy versus channel-launch-blueprint or when to reach for this over sibling planning/writing tools. Usage is inferable rather than stated.

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.

Resources