Skip to main content
Glama

DevTune MCP

by ai.devtune
OverviewDiscussionsAdmin

devtune_get_actions

Get the actions for a project. status is suggested (DevTune proposed it, nobody has decided), accepted (the team wants it done), live (the page is published and its measurement window is open) or archived (taken off the queue by the team); blocked is true on accepted work the team has marked blocked. Suggested actions expose the same nullable opportunity percentile, percentileStatus and percentileScope as REST (signal_family compares like signals; families are interleaved), Reach, Gap, Confidence, family (including citation defence), estimated state, measured facts, and locked-page steering source. A null percentile carries percentileStatus insufficient_reach when reach is null, sensor coverage is absent, or estimated reach is zero. It carries percentileStatus no_measured_gap when every product in the family is zero and reach is non-null and not estimated-zero. Numeric percentiles omit the status. percentilePoolSize counts rankable candidates in the full family before selection or pagination. A size of one means Only ranked opportunity of this type, never Top 1%. Older records omit the pool size; do not infer singleton status from percentile 100 or the returned page. Positive-product candidates are seated before zero-product candidates. Citation-defence normalization is matched_cohort_executions when the cohort rollup is published or window_executions when the matched cohort is not published yet. Both compare citations per successful prompt execution; matched-cohort loss reports one-window-only composition changes and states matched coverage of earlier citations. Suggested actions come first and follow persisted portfolioRank ascending, nulls last, and no action exposes a legacy scalar score. Context detail includes bounded audit assessment dates, factor checks and prompt-coverage limits, plus structured Google eligibility dimensions when entitled live evidence is available. Every action carries assignedTo (its owner's user id, null when unassigned) and ownerName; change either with devtune_update_action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number. Defaults to 1.
statusNoFilter by action status. Omit it to get every status.
channelNoFilter by recommended channel.
pageSizeNoResults per page (1-100). Defaults to 25.
priorityNoFilter by priority level.
detailLevelNoResponse detail level. summary is default. context adds bounded why-now context, available opportunity evidence, metrics, top evidence with structured Google eligibility when available, the external pages winning its prompts (competitor and third-party, in the order briefs study them), brief readiness, and follow-up links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detailLevel / description
      Previous value: -"Response detail level. summary is default. context adds bounded why-now context, available opportunity evidence, metrics, top evidence with structured Google eligibility when available, brief readiness, and follow-up links."New value: +"Response detail level. summary is default. context adds bounded why-now context, available opportunity evidence, metrics, top evidence with structured Google eligibility when available, the external pages winning its prompts (competitor and third-party, in the order briefs study them), brief readiness, and follow-up links."
  2. Changed3 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Filter by public action status. Use active for recommendations and backlog/in_progress/blocked/done/canceled for adopted work. The aliases open, completed, and dismissed map to backlog, done, and canceled."New value: +"Filter by action status. Omit it to get every status."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "active",
-  "backlog",
-  "in_progress",
-  "blocked",
-  "done",
-  "canceled",
-  "open",
-  "completed",
-  "dismissed"
-]New value: +[
+  "suggested",
+  "accepted",
+  "live",
+  "archived"
+]
    • removedInput schema / properties / surface
      Removed value: -{
-  "description": "Filter to the recommendation feed or the adopted backlog surface.",
-  "enum": [
-    "recommendation",
-    "backlog"
-  ],
-  "type": "string"
-}
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so richly: it discloses sort order (suggested actions first, portfolioRank ascending, nulls last), null-percentile/status behavior, percentilePoolSize semantics, and citation-defence normalization rules. It stops short of permissions, rate limits, or failure modes, so it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and the dense content is arguably justified given there is no output schema to explain return fields. However, it is a run-on wall of text with no structural separation, making it hard to scan for the actionable parts.

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?

With no output schema, the description correctly takes on explaining returned fields, ordering, and null-handling, so it is largely complete for a six-parameter filtered-read tool. The main gaps are the lack of differentiation from sibling list tools and any mention of auth or error behavior.

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 every parameter is already documented, establishing a baseline of 3. The description adds real meaning for the status enum values (suggested/accepted/live/archived) and for context-level output, but it does not clarify channel, priority, or page semantics beyond 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?

The opening sentence gives a clear verb+resource ('Get the actions for a project') and the status/field discussion confirms this is a read/list tool. However, it never distinguishes itself from close siblings like devtune_get_prompt_actions or devtune_create_prompt_action, so an agent must infer which action-type this returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for retrieving other action variants. The only routing hint is a trailing 'change either with devtune_update_action,' which addresses mutation rather than when to call this tool.

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

All DevTune MCP toolsInspect
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