GBPly

Request adding a post to an evergreen campaign

request_add_to_evergreen

Destructive

Ask the user to approve adding one post to an existing evergreen library. Returns an approval link.

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": {
      "campaign_id": "<campaign_id>",
      "content": "<content>"
    },
    "name": "request_add_to_evergreen"
  }
}

Input Schema

Name	Required	Description
`content`	Yes
`cta_url`	No	Required for every button type except CALL.
`cta_type`	No
`image_url`	No	Public JPEG/PNG under 5MB.
`post_type`	No	Default STANDARD.
`campaign_id`	Yes
`coupon_code`	No
`event_title`	No
`event_end_date`	No
`event_end_time`	No
`event_start_date`	No	YYYY-MM-DD
`event_start_time`	No	HH:mm
`terms_conditions`	No
`redeem_online_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description usefully adds that the mutation is deferred behind a user approval step and that an approval link is returned. It does not say what approval actually does to the library, whether repeat calls create duplicate requests, or how long the link lives, which matters given the destructive/non-idempotent profile.

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?

Two short sentences with the action front-loaded and the return value second; nothing is wasted. It is arguably too terse for a 14-parameter tool, but there is no filler to cut.

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 destructive, open-world, non-idempotent tool with 14 parameters, no output schema, and low schema coverage, the definition is far too thin. An agent learns what the tool requests but not what the returned link is for, what approval triggers, or how to populate the many content/CTA/event fields.

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

Parameters2/5

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

With 14 parameters and only 36% schema description coverage, the description should carry meaning, but it mentions no parameters at all. Field interactions such as cta_type driving cta_url, post_type EVENT requiring event dates, or coupon_code pairing with OFFER are undocumented in either place.

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?

States a specific verb and resource: adding one post to an existing evergreen library, via a user-approval request. The 'existing library' qualifier implicitly separates it from request_create_evergreen_campaign, though no sibling is named explicitly.

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?

There is no explicit when-to-use guidance and no stated alternatives among the many request_* siblings. Only the mild implication that the campaign must already exist ('existing evergreen library') hints at prerequisites; when-not conditions and the relationship to request_create_post or request_create_evergreen_campaign are left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GBPly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?