Grigora

update_page

Destructive

Update a page's metadata: title (name), slug, SEO fields, and custom HTML. Only provided fields are updated. Slug must be unique in the project.

Args: project_id: The project ID. page_id: The page ID. name: Page display name/title (leave empty to keep current). slug: URL slug (leave empty to keep current). seo_meta_title: SEO meta title (leave empty to keep current). seo_meta_desc: SEO meta description (leave empty to keep current). seo_meta_image: SEO/OG image URL or empty to keep current. no_index: Whether to set noindex for search engines (None = keep current). custom_header_html: Custom HTML in head (leave empty to keep current). custom_footer_html: Custom HTML before closing body (leave empty to keep current).

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": {
      "project_id": "<project_id>",
      "page_id": "<page_id>"
    },
    "name": "update_page"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`slug`	No
`page_id`	Yes
`no_index`	No
`project_id`	Yes
`seo_meta_desc`	No
`seo_meta_image`	No
`seo_meta_title`	No
`custom_footer_html`	No
`custom_header_html`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: partial-update semantics ('only provided fields are updated') and a slug-uniqueness validation constraint. It stops short of permissions or failure modes, but this is solid added value.

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-loads purpose, then behavior constraints, then a parameter list. Every line earns its place given 0% schema coverage; repetition of '(leave empty to keep current)' is informative rather than filler, though the block is somewhat long.

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?

A mutation tool with annotations, an output schema (so return values need not be described), and all parameters documented in the description. Complete for correct invocation, missing only siblings routing and permission/error details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden, and it does so well: each of the 10 parameters is documented with meaning and the 'leave empty to keep current' default behavior. This fully compensates for the undocumented schema.

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 ('Update a page's metadata') and enumerates the affected fields (title, slug, SEO fields, custom HTML). Clear enough for an agent to act, though it does not distinguish itself from siblings like update_cms_post or update_directory_item.

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?

Provides useful constraints ('Only provided fields are updated', 'Slug must be unique in the project'), implying PATCH-style partial updates. However, it gives no explicit when-to-use vs alternatives, no prerequisites, and does not point to get_page for reading current values.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Grigora tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?