Skip to main content
Glama

Update SEO

update_seo
DestructiveIdempotent

Update the SEO metadata for a page — title tag, meta description, OG image, and target search term (the keyword the page should rank for).

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Overwrites a page's title, description and SEO settings on the DRAFT — non-additive, so destructive by the MCP definition; idempotent; closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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": {
      "site_id": "<site_id>",
      "page_slug": "<page_slug>"
    },
    "name": "update_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoPage title tag (under 60 chars ideal)
site_idYes
og_imageNoOpen Graph image URL
page_slugYes
descriptionNoMeta description (150-160 chars ideal)
target_search_termNoThe search phrase this page targets, e.g. "emergency plumber austin tx" — shown as Target Search Term in Get Found. Give each page its OWN term; two pages targeting the same phrase compete against each other in Google. Pass "" to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare destructive=true and idempotent=true, so the bar is lower, yet the description goes further by explaining WHY — the update is non-additive because it overwrites existing title/description/SEO settings — and by scoping the blast radius to the draft rather than the live site. That is exactly the kind of consequence information an agent needs before calling a destructive tool.

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?

The definition is front-loaded: the action and field list come first, then the draft-versus-live consequence. The "Why:" clause is slightly meta and reads like annotation rationale, but it carries genuine behavioral content rather than repetition, so nearly every sentence earns its place.

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 six parameters, no output schema, and no enums, the description supplies the things the schema cannot: mutation semantics, draft scope, and the publish step that makes changes live. Field-level detail is left to the schema, which is reasonable at 67% coverage; only the unannotated site_id/page_slug identification is 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?

Schema description coverage is 67%, which sets the baseline at 3. The description clarifies target_search_term as "the keyword the page should rank for," but the schema entry for that field is already more detailed (examples, the two-pages-competing warning, empty-string clearing), and site_id/page_slug/og_image get no added meaning from the description at all.

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 opens with a specific verb and resource ("Update the SEO metadata for a page") and enumerates exactly which fields are in scope — title tag, meta description, OG image, and target search term — with a parenthetical defining the one ambiguous field. An agent can distinguish this from update_block, update_design, or update_header without opening any 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 establishes the crucial operational context: edits land on the DRAFT and the live site only changes when the user confirms publish_site, which effectively tells the agent when this tool is and isn't the final step. It does not name an explicit alternative for SEO edits, but no sibling in the list plausibly covers this same scope, so the gap is minor.

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.