DevTune MCP

devtune_update_action

DestructiveIdempotent

Rename an action, set its owner, change its channels, or edit its description. Works on accepted and live actions; restore an archived action first. DevTune's suggestions, including dismissed and snoozed ones, keep their details and have no owner, so accept one first. assignedTo is a member's user id or sign-in email; pass null to unassign. channels is the full set of channels that own the work, at least one; it replaces the current set, and order does not matter. description only changes on an accepted action the team created: DevTune's actions keep the description their evidence wrote, and a live action's description is fixed until the action is reopened. Owner ids and names are on devtune_get_actions. Returns the action with description, channels, assignedTo and ownerName. Does not notify the owner or mark the brief out of date.

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": {
      "actionId": "<actionId>"
    },
    "name": "devtune_update_action"
  }
}

Input Schema

Name	Required	Description
`title`	No	New title. Omit to keep the current title.
`actionId`	Yes
`channels`	No	Every channel that owns the work; replaces the action's channels. Omit to keep the current channels.
`assignedTo`	No	The new owner as a user id or the email they sign in with, or null to unassign. Omit to keep the current owner.
`description`	No	New description. Only for an accepted action the team created. Omit to keep the current description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 10, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / actionId

Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
+  "type": "string"
+}

addedInput schema / properties / assignedTo

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
+          "type": "string"
+        },
+        {
+          "format": "email",
+          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The new owner as a user id or the email they sign in with, or null to unassign. Omit to keep the current owner."
+}

addedInput schema / properties / channels

Added value: +{
+  "description": "Every channel that owns the work; replaces the action's channels. Omit to keep the current channels.",
+  "items": {
+    "enum": [
+      "docs",
+      "content",
+      "devrel",
+      "pr",
+      "engineering",
+      "product",
+      "other"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / description

Added value: +{
+  "description": "New description. Only for an accepted action the team created. Omit to keep the current description.",
+  "maxLength": 10000,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / title

Added value: +{
+  "description": "New title. Omit to keep the current title.",
+  "maxLength": 500,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "actionId"
+]
```

AddedSep 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true) it discloses that channels replaces the whole set, that description edits are blocked on DevTune-authored and live actions, that the owner is not notified, and that the brief is not marked out of date. These are real side-effect and constraint details the annotations cannot express, though it does not discuss failure modes or partial-update behavior.

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?

Purpose is front-loaded, then state preconditions, then per-parameter rules, then return and side effects — a sensible ordering with no filler sentences. It is dense and long-ish, but nearly every clause carries a constraint the agent needs.

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 destructive multi-field mutation with no output schema, it covers eligibility, replacement semantics, return shape (action with description, channels, assignedTo, ownerName), and non-effects (no owner notification, brief not stale). An agent has enough to call it correctly and predict consequences.

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 already 80%, yet the description adds meaning: assignedTo accepts a user id or sign-in email with null to unassign, channels must contain at least one entry and order is irrelevant, and the description field's eligibility rules are explained rather than merely asserted. It stops short of covering actionId or title semantics.

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?

Opens with specific verbs and the resource: rename, set owner, change channels, edit description on an action. This clearly separates it from siblings like devtune_change_action_status (status transitions) or devtune_get_actions (reads), so an agent can route without opening the 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?

Gives explicit preconditions and exclusions: only accepted and live actions, archived actions must be restored first, and DevTune suggestions (including dismissed/snoozed) must be accepted before editing. It also points to devtune_get_actions as the source of owner ids and names.

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

All DevTune 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.

Resources

Need Help?