Skip to main content
Glama
Sign In
ThumbGate

ThumbGate

by IgorGanapolsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Plan Chatgpt Ads Readiness

plan_chatgpt_ads_readiness
Read-only

Prepares intent clusters, ad copy, proof links, UTM tracking, and launch gates for testable ChatGPT Ads campaigns, ensuring measurement and approval before launch.

Instructions

Prepare ThumbGate intent clusters, ad copy, proof links, UTM measurement, and launch gates for ChatGPT Ads Manager tests.

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

Input Schema

NameRequiredDescriptionDefault
offerNoOffer to advertise, such as Pro or Workflow Hardening Sprint.
budgetNoInitial test budget.
audienceNoAudience segment to target.
keywordsNoHigh-intent conversational queries.
proofLinksNoProof URLs required by ad claims.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.23.1
  2. Removedv1.21.2
  3. Addedv1.16.19

TDQS

B3.1/5.0
Behavior1/5

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

Description says 'Prepare' which implies creating/writing, contradicting readOnlyHint=true annotation. No additional behavioral context provided (e.g., auth, side effects).

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?

Single sentence front-loaded with purpose, though the contradiction reduces overall value. Still concise and structured well.

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?

No output schema, 5 parameters, but description lacks detail on process, return format, or how components are prepared. Contradiction with annotations further undermines completeness.

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%, so baseline is 3. Description merely lists components already covered by parameters, adding no new semantic depth.

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 clearly states the tool prepares specific ad components (intent clusters, ad copy, etc.) for ChatGPT Ads Manager tests, using a specific verb 'prepare' and a clear resource, distinguishing it from other plan_ tools.

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?

Description implies use when setting up ads but lacks explicit guidance on when to use versus alternatives, no exclusions or prerequisites mentioned.

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