Skip to main content
Glama
agencian1

mcp-runrunit

by agencian1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

runrunit_update_comment

Update a Runrun.it comment with standard sections like scope, implementation, affected files, and validation steps. Use it to revise task comments and optionally append before/after evidence URLs.

Instructions

Update a comment on Runrun.it. Send the same standard template sections as runrunit_create_comment (Escopo, Como foi feito, Quais arquivos/configurações foram afetadas, Como validar, Links). Plain text and raw URLs only. Optional url_antes and url_depois are appended at the end of Links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesComment ID
linksYesReference links for validation, including preview and PR/MR URLs. Raw URLs only, no Markdown.
escopoYesContext of the implementation or fix. Example: correção no checkout. Plain text only.
url_antesNoOptional. URL of the before state or evidence image. When set, the server appends 'Antes: <url>' at the end of Links. Capture evidence with the registrar-evidencias skill first.
url_depoisNoOptional. URL of the after state or evidence image. When set, the server appends 'Depois: <url>' at the end of Links.
como_validarYesStep-by-step test instructions, at least two non-empty lines. Example: "1. Acesse o link de preview:\n2. Navegue até a sessão Y". Plain text only.
como_foi_feitoYesWhether the change was code or panel configuration, and what changed. Example: Atualizei o código X do arquivo xyz.ts. Plain text only.
arquivos_configuracoesYesPaths or links of the affected files or settings. Example: src/checkout/xyz.ts. Plain text and raw URLs only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.0.0
    • addedInput schema / properties / arquivos_configuracoes
      Added value: +{
+  "description": "Paths or links of the affected files or settings. Example: src/checkout/xyz.ts. Plain text and raw URLs only.",
+  "type": "string"
+}
    • addedInput schema / properties / como_foi_feito
      Added value: +{
+  "description": "Whether the change was code or panel configuration, and what changed. Example: Atualizei o código X do arquivo xyz.ts. Plain text only.",
+  "type": "string"
+}
    • addedInput schema / properties / como_validar
      Added value: +{
+  "description": "Step-by-step test instructions, at least two non-empty lines. Example: \"1. Acesse o link de preview:\\n2. Navegue até a sessão Y\". Plain text only.",
+  "type": "string"
+}
    • addedInput schema / properties / escopo
      Added value: +{
+  "description": "Context of the implementation or fix. Example: correção no checkout. Plain text only.",
+  "type": "string"
+}
    • addedInput schema / properties / links
      Added value: +{
+  "description": "Reference links for validation, including preview and PR/MR URLs. Raw URLs only, no Markdown.",
+  "type": "string"
+}
    • removedInput schema / properties / text
      Removed value: -{
-  "description": "New comment text",
-  "type": "string"
-}
    • addedInput schema / properties / url_antes
      Added value: +{
+  "description": "Optional. URL of the before state or evidence image. When set, the server appends 'Antes: <url>' at the end of Links. Capture evidence with the registrar-evidencias skill first.",
+  "type": "string"
+}
    • addedInput schema / properties / url_depois
      Added value: +{
+  "description": "Optional. URL of the after state or evidence image. When set, the server appends 'Depois: <url>' at the end of Links.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "text"
-]New value: +[
+  "id",
+  "escopo",
+  "como_foi_feito",
+  "arquivos_configuracoes",
+  "como_validar",
+  "links"
+]
  2. First observedv1.8.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior: the required template sections, the plain-text/raw-URL constraint, and that url_antes/url_depois are appended to the end of Links. It omits whether the update replaces the whole comment body, whether auth/permissions are required, and whether omitted optional fields are cleared.

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?

Three short sentences, front-loaded with the action and resource, then the template constraint and the url detail. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the template and URL conventions but leaves key gaps: whether all six required fields must be resupplied (full replace vs merge) and permission/authorization expectations.

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 baseline is 3. The description restates the template sections and the url_antes/url_depois append behavior, but that behavior is already documented in the schema, so it adds little beyond what the structured field provides.

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 comment on Runrun.it') and ties itself to runrunit_create_comment by naming the shared template, which orients the agent among the comment siblings. It does not explicitly differentiate from delete_comment/get_comment, though 'update' makes the intent unambiguous.

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?

It establishes context by pointing to the create_comment template, implying 'use this when a comment already exists and needs revision', and notes the optional url_antes/url_depois behavior. There is no explicit when-to-use-this-vs-alternatives statement or stated prerequisite (e.g. needing an existing comment ID).

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

Deploy Server

Other Tools