Skip to main content
Glama

Refresh workspace playbook

campaignstack_refresh_workspace_playbook

Regenerate the workspace playbook from current campaigns, ICPs, personas, and the company profile. User-authored passages are preserved and prior text is snapshotted. A refresh that did not run (no live campaign, out of credits, a managed playbook) comes back with ok false and the reason; a section left empty because it stated company facts the profile does not hold comes back as a warning.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that user-authored passages survive, prior text is snapshotted, failures return ok=false with a reason, and missing company facts surface as a warning rather than silently omitting content. That preservation and snapshot behavior is exactly the reassurance an agent needs for a non-idempotent mutation. It stops just short of covering cost or permission details beyond the 'out of credits' mention.

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?

Three sentences, purpose front-loaded, followed by side effects and then failure semantics — no wasted wording. The final warning sentence is slightly dense but still readable.

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 mutation tool with an output schema present, the definition covers sources, side effects, failure outcomes, and warnings, which is nearly everything an agent needs to call it correctly. Only cross-tool routing to the propose-change sibling is left unaddressed.

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?

The single workspaceId parameter is already fully documented in the schema, including key-prefix and defaulting behavior, and the description adds nothing further about it. Baseline 3 applies when schema coverage is complete.

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: 'Regenerate the workspace playbook from current campaigns, ICPs, personas, and the company profile,' which tells an agent exactly what is produced and from what inputs. It does not explicitly distinguish itself from the close sibling campaignstack_propose_workspace_playbook_change, so sibling routing is left partly to inference.

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 'did not run' conditions (no live campaign, out of credits, managed playbook) act as implicit preconditions telling the agent when the call will not succeed. However, there is no explicit when-to-use statement and no named alternative for partial edits, where propose_workspace_playbook_change would presumably be the right tool.

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