Skip to main content
Glama

Edit a request

updateRequest
Destructive

Change title, schema, sections, reason or theme until the first response. addRecipients, expiresIn (a new expiry counted from now) and notifyEmail work until the request is closed, expired or complete. Existing links keep working. Added recipients are not emailed; remind emails them by recipientId.

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": {
      "requestId": "<requestId>"
    },
    "name": "updateRequest"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoColours, font and layout: https://runitby.app/llms.txt ("Theme").
titleNo
reasonNoNew approval reason.
schemaNo
sectionsNo
expiresInNo
requestIdYes
notifyEmailNoEmail the account owner (your user) a summary and a dashboard link: "each" on every answer (until the plan's email limits, then only the end), "complete" once when the request completes or expires. Left out: the account's default from the dashboard ("off" unless changed).
addRecipientsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing time-windowed field mutability, that existing links keep working, that added recipients are not emailed, and that remind handles recipientId emails. These are exactly the side-effect and lifecycle details an agent needs before mutating a request.

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?

Dense but front-loaded with the mutability window first, then the closed/expired window, then side-effect notes. No filler, though the compression makes some sentences (the addRecipients/expiresIn/notifyEmail clause) slightly hard to parse.

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?

For a 9-parameter mutation tool with nested objects and no output schema, the description covers the important lifecycle and side-effect context. It leaves the shape of theme/schema/sections largely to schema-level pointers rather than explaining them, a minor gap.

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?

With only 33% schema coverage, the description carries most of the parameter meaning: expiresIn is a new expiry counted from now, notifyEmail behavior, addRecipients does not email. The nested theme/schema/sections semantics are only lightly touched, so it does not fully close the gap.

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 (change) and resource (request) and enumerates the mutable fields: title, schema, sections, reason, theme. It is clearly an edit operation distinguishable from closeRequest or createRequest, though it does not explicitly name sibling tools as alternatives.

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 concrete conditions: title/schema/sections/reason/theme only until the first response; addRecipients/expiresIn/notifyEmail until closed, expired or complete. This tells the agent when the tool will and won't work, and hints at the remind alternative, but there is no explicit 'use X instead when...' routing.

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.

Resources