Skip to main content
Glama

Scheduled campaigns

campaign_schedule
Read-onlyIdempotent

Retrieve campaigns scheduled to go out from Booksy Biz and optionally bypass the local cache to get fresh results.

Instructions

Campaigns scheduled to go out.

Input Schema

NameRequiredDescriptionDefault
freshNoSkip the local cache

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond that – no mention of what the schedule window is, what fields are returned, or how the open-world lookup behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, but brevity here comes from omission rather than economy. There is no front-loaded scope or qualifier to anchor the agent.

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?

There is no output schema, so the description should at least indicate what is returned (a list of campaigns with schedule times, status, etc.). It also leaves the cache/`fresh` trade-off and the time window unaddressed, which is insufficient even for a simple list tool.

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 description coverage is 100% and the single `fresh` parameter is documented there ("Skip the local cache"). The description adds no meaning on top of that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Campaigns scheduled to go out" only rephrases the tool name and title (Scheduled campaigns) rather than stating a verb and resource. It never says it retrieves/lists scheduled campaigns, nor distinguishes it from siblings like campaign_groups, campaign_details, or campaign_estimate.

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?

No when-to-use, when-not-to-use, or alternative is mentioned. With many campaign siblings present, the description gives the agent no basis for choosing this tool over campaign_details or campaign_groups.

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