sheetrender-mcp

Create a continue link

create_continue_link

Create a link to the template's page on the SheetRender website with the user's rows loaded, so they can be kept as a SheetRender project. Call this only when the user asks to continue on the website, to keep or save the rows, to repeat or schedule the job, or to have the documents delivered by email; do not call it otherwise. Accepts up to 100 rows. The rows are stored until they are loaded into a project or for 7 days, whichever comes first, and the link expires after 7 days.

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": {
      "template": "<template>",
      "rows": "<rows>"
    },
    "name": "create_continue_link"
  }
}

Input Schema

Name	Required	Description
`rows`	Yes	The user's rows, keyed by field key, at most 100.
`title`	No	Optional name for this set of documents, e.g. "Q3 volunteer certificates".
`template`	Yes	Template key from list_document_templates.

Output Schema

Name	Required	Description	Default
`expires_at`	Yes
`rows_saved`	Yes
`continue_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent, closed-world), and the description adds real behavioral context the annotations do not: rows are retained until loaded or 7 days, and the link itself expires after 7 days. It stops short of describing what happens if a link is regenerated or how the link is returned, but the retention/expiry disclosure is substantive.

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?

Purpose is front-loaded, followed by the usage gate, then limits and retention in two short concluding sentences. No filler; every sentence carries distinct information.

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?

An output schema exists, so return values need not be described. For a creation tool the description covers the required ingredients an agent needs: when to invoke, the row cap, and the persistence/expiry window. Nothing material is 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 description coverage is 100%, so the schema already documents all three parameters. The description's 'Accepts up to 100 rows' merely restates the schema's maxItems cap and adds no syntax or format detail, so the baseline of 3 applies.

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 ('Create a link to the template's page on the SheetRender website with the user's rows loaded') plus the outcome (kept as a SheetRender project). This is clearly distinguishable from render_documents and list_document_templates 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 Guidelines5/5

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

Explicitly enumerates the trigger intents (continue on the website, keep/save rows, repeat or schedule the job, email delivery) and closes with 'do not call it otherwise', which is an explicit exclusion. This is the strongest form of when/when-not guidance.

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

All sheetrender-mcp 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.