Skip to main content
Glama

getWritingGuidelines

CALL THIS FIRST before you write or rewrite ANY public text (pages, team or any other collection with public text you have tools for) — once per task and target collection/locale. Returns the complete writing brief the site's own AI uses: brand voice and addressing, the house writing rules (internal — follow them, never state them), fixed terms that stay unchanged in every language, the terms & language rules of the requested locale, available placeholders, the author voice (with teamAuthor), the site-wide SEO rules (branding.aiSeoRules), the SEO meta rules (title/description length, title suffix), the keywords already taken in this locale (do not reuse) with their doc ids for internal links, the fields of the collection and how to write them via MCP. Pass topic (a few words or your draft) so the most related taken keywords come first. A long brief comes in parts: when the first line shows parts > 1, call again with the same arguments and part: 2, 3 … and read ALL parts before writing. The response is INTERNAL guidance — never publish it.

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": {
      "collection": "<collection>"
    },
    "name": "getWritingGuidelines"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoWhich part of a long brief to return (default 1). The first line of every part states `part` and `parts`.
topicNoWhat you are writing about (keywords or your draft) — the taken keywords most related to it come first.
localeNoLocale you are writing (default: the site default locale). Call again per locale.
collectionYesTarget collection slug, e.g. "pages" — any collection you have find/update tools for.
teamAuthorNoTeam member id when the text is published AS a person (authorMode "person"); adds their voice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / collection / description
      Previous value: -"Target collection slug, e.g. \"pages\", \"posts\", \"glossary\", \"faqs\"."New value: +"Target collection slug, e.g. \"pages\" — any collection you have find/update tools for."
  2. Changed1 schema field changed
    • addedInput schema / properties / part
      Added value: +{
      +  "description": "Which part of a long brief to return (default 1). The first line of every part states `part` and `parts`.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"What you are writing about (keywords or your draft) — ranks the knowledge rules for it."New value: +"What you are writing about (keywords or your draft) — the taken keywords most related to it come first."
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose key traits: the response is internal-only and must never be published, house rules are to be followed but not stated, taken keywords must not be reused, and long briefs arrive in numbered parts. It stops short of noting size/latency expectations or what happens for an unknown collection slug, so it is strong but not exhaustive.

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?

Front-loaded with the imperative 'CALL THIS FIRST', and every clause maps to a real behavior (pagination, internal-only, taken keywords). It is a single dense run-on paragraph with stacked parentheses and em-dashes, which makes it harder to scan than it needs to be for content this rich.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter read tool with no output schema, the description fully covers what comes back, how it is chunked, and the handling constraint (never publish). Nothing an agent needs to invoke and consume the result correctly appears to be missing.

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 each parameter already carries its own documented meaning. The description echoes those semantics (topic ordering, part pagination, per-locale calls, teamAuthor voice) and adds only the framing that `collection` is any collection with find/update tools — marginal value beyond the schema.

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?

States a specific verb and resource ('Returns the complete writing brief') and enumerates exactly what the brief contains (brand voice, house rules, fixed terms, locale rules, placeholders, SEO rules, taken keywords, collection fields). It clearly separates itself from the find*/report* siblings, which retrieve content rather than authoring guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit trigger ('CALL THIS FIRST before you write or rewrite ANY public text'), explicit frequency ('once per task and target collection/locale'), and explicit follow-up behavior when `parts` > 1. The agent knows exactly when to call, how often, and how to complete a multi-part fetch without guessing.

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