Skip to main content
Glama

Create several wiki pages

create_wiki_pages

Start up to 25 pages in one call, each exactly as create_wiki_page would. A page whose name is already there is returned rather than doubled, and one page that is refused doesn't stop the rest. Returns: One result per page, in order: its slug and whether it already existed, or why it was refused.

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": "<campaign>",
      "pages": "<pages>"
    },
    "name": "create_wiki_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYesThe pages to start.
campaignYesThe campaign, by its slug (what its link says) or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses two behaviors an agent could not otherwise know: duplicate names are resolved by returning the existing page, and a refused page does not abort the rest of the batch. That partial-failure semantics is genuinely useful. The dedup-by-name behavior sits slightly in tension with idempotentHint=false, though it is not a direct contradiction since the hint speaks to repeated calls generally rather than name collisions.

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

Conciseness5/5

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

Two sentences, front-loaded with the batch scope and cap, followed by failure/return semantics. No filler, no restating of the title, and every clause carries information an agent needs.

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?

With no output schema, the description steps in to describe the per-page result shape (slug plus existed-or-refused reason, in order), and it covers batch limits, dedup, and partial failure. What remains unstated is minor, such as whether campaign-level validation failures behave like per-page refusals.

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 every nested page field is documented in the schema, so the description carries little param burden. It only adds the batch cap and the fact that nested page objects behave identically to create_wiki_page parameters, which is a modest supplement. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb and resource ('Start up to 25 pages in one call') and explicitly contrasts the batch form with the single-page sibling ('each exactly as create_wiki_page would'). An agent can distinguish this from create_wiki_page without inspecting 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 Guidelines4/5

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

It clearly implies the batch use case and anchors semantics to the single-page tool, and the 25-item cap tells the agent when the call must be split. It stops short of an explicit rule such as 'use create_wiki_page when adding only one page', so the when-not side is inferred rather than stated.

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.