OrgLines

Website: Update text

website_update_text

Destructive

Change a block's heading, subheading or text on an existing site, exactly as the person worded it; and/or replace the site's services list with prices ('services': the owner's own items — a price ONLY if they named one, never invented). Runs propose→confirm. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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

Input Schema

Name	Required	Description
`text`	No
`block`	No	Which block: its id from website_publish_status, its type (hero, gallery, services, testimonials, team, contacts, footer…) or the owner's word for it (шапка, галерея, відгуки, послуги).
`heading`	No
`website`	No	Site id, name or subdomain. Optional when the workspace has one site.
`services`	No
`subheading`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already flag a destructive write, and the description adds substantial beyond that: the propose→confirm two-phase flow, the returned status='confirmation_required', action_id and plan_token, and the fact that no write occurs until confirm_action runs. That is exactly the behavioral context an agent needs before invoking a mutating 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?

Front-loads the action and scope in one dense sentence, then the confirmation contract. The parenthetical lists and quoted constraints make it slightly heavy, but every clause carries operational meaning.

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 usefully explains the response shape and next step. It leaves open edge cases such as an unmatched block or whether existing text is fully overwritten, but covers the essentials for a 6-parameter mutation tool.

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

Parameters4/5

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

Schema coverage is only 33%, so the description must carry weight, and it does: it maps 'block' to heading/subheading/text targets, clarifies that 'text' should be verbatim owner wording, and defines 'services' as the owner's own items with prices only when stated. It does not touch the maxLength or website-fallback semantics, which the schema covers separately.

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: changing a block's heading, subheading or text on an existing site, and optionally replacing the services list with prices. It is clearly distinct from siblings like website_update_contacts or website_add_reviews, though it does not name an alternative tool directly.

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?

Gives clear operating conditions: write the text 'exactly as the person worded it' and include a price 'ONLY if they named one, never invented.' It also explains that the tool only proposes and requires confirm_action. It stops short of naming sibling tools to use instead for other site edits.

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

All OrgLines 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?