Skip to main content
Glama

The Profound Agency

Submit a campaign brief

submit_campaign_brief

Submit a paid media brief for a client and have the team come back with a quote — impressions, placements and a recommendation. Use this for advertising campaigns (display, video, Connected TV, social, search, audio, out-of-home), which are priced per campaign; use create_order instead for buying a press placement from the publisher catalogue, which has a fixed price. Nothing is purchased or committed here: it opens a conversation, and a human prices it and replies. Pick capabilities when you know the outcome the client wants, products when you know the channels, or both. The response scores the brief's completeness (0-100) and lists the most valuable missing details — the brief is filed regardless, so ask the human for the gaps to get priced faster. Confirm the details with a human before sending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoWhat the campaign should achieve.
notesNoAnything else the team should know.
budgetNoMonthly budget, or a range.
timingNoWhen they want to start.
contactYes
channelsNoSpecific product slugs, as returned by search_placements or list_channels.
geographyNoWhere it should run — cities, states, ZIPs or a radius.
referredByNoWho you are — your agent, agency or product. Recorded on the brief as an unverified claim so we can see which agents send work.
capabilitiesNoOutcomes the client wants, by slug. Use list_capabilities to see them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations say readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive. The description adds crucial context beyond that: nothing is purchased or committed, it opens a conversation, a human prices it and replies, and confirmation with a human is required before sending. It also explains the completeness score and the missing-details list. Slightly short of 5 because it doesn't state what happens on a duplicate submission or the non-idempotent consequence.

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?

Front-loads purpose and sibling differentiation, then behavior, then selection guidance. Dense but each sentence earns its place. Slightly overlong with multiple clauses in the final sentence, but 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?

Covers purpose, routing, non-commitment behavior, response contents, and human-confirmation requirement for a 9-parameter nested-object tool with no output schema. Complete enough to invoke correctly, though it doesn't describe error or validation behavior on the nested contact object.

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

Parameters4/5

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

Schema coverage is 89%, so the schema documents most parameters. The description adds meaning the schema does not: that capabilities are for known outcomes and channels are for known channels, and the routing to list_capabilities and search_placements/list_channels. This is useful disambiguation rather than restatement.

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?

States a specific verb and resource ('Submit a paid media brief'), and explicitly distinguishes itself from the sibling create_order by naming it and the condition that selects it (press placement, fixed price). An agent can route between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (advertising campaigns across display/video/CTV/social/search/audio/OOH, priced per campaign) and when-not-to-use, naming create_order and the alternative condition. Adds selection guidance between capabilities vs products vs both.

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