Conecto

Edit page sections

help_center_edit_sections

Add, update, move, duplicate or remove sections on one page of the DRAFT, in order. add: {op:"add", type, props?, style?, at?}; update: {op:"update", id, props?, style?} (merged into what is there); move: {op:"move", id, to}; duplicate / remove: {op, id}. Returns the id of anything added and the page’s new order. Costs $0.001 per call; nothing if it fails.

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": {
      "page": "<page>",
      "ops": "<ops>"
    },
    "name": "help_center_edit_sections"
  }
}

Input Schema

Name	Required	Description
`ops`	Yes
`rev`	No	The draft revision you last read (from any tool that returns `rev`). If the draft changed since, nothing is saved and you get the current revision to re-read.
`page`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description discloses behavior well beyond the annotations: exact per-call cost ($0.001, free on failure), the all-or-nothing failure mode, return values (new ids and the page's new order), and merge semantics for update. Annotations already cover the safety profile, but these cost and failure semantics are genuinely additive.

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?

Dense, front-loaded single paragraph with zero wasted words; the op grammar is compact and the cost/return notes are ordered after the core purpose.

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 batched mutation tool with no output schema, the description covers return values, failure semantics, cost, and per-op payload structure. Concurrency via `rev` is documented in the schema, so nothing critical is missing.

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 description coverage is only 33%, and the description compensates by spelling out the shape of each op (add fields, update with merge semantics, move with `to`, duplicate/remove with just `id`). It does not explain `rev` or the page enum values, which are left to the 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 specific verbs (add, update, move, duplicate, remove) and the exact resource (sections on one page of the DRAFT). The scope is clear enough to distinguish it from sibling tools like help_center_save_article or help_center_publish, but it never names those alternatives explicitly.

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?

Clear context that this operates only on the DRAFT and applies ops 'in order', which implicitly tells the agent not to use it on published pages. However, it offers no explicit when-not guidance or pointers to sibling tools for related work.

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

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