DevTune MCP

devtune_get_action_events

Read-onlyIdempotent

List who changed an action's title, owner, channels, description or published pages, newest first. Each event has a kind (renamed, owner_set, owner_cleared, channels_changed, description_changed, published_page_added or published_page_removed), from and to values (owners as user ids, channels as arrays, pages as URLs), the actor (a user with their id and name while they are still a member, an api_key with its key id, or system for DevTune) and createdAt. Lifecycle moves such as accepting, going live or archiving are not events; read them from devtune_get_actions. History starts when recording began, so older edits are not listed. Pass nextCursor back as cursor for the next page.

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_get_action_events"
  }
}

Input Schema

Name	Required	Description
`limit`	No	The same setting as pageSize. Send either.
`cursor`	No	nextCursor from the previous page.
`actionId`	Yes	UUID of the action.
`pageSize`	No	Events per page (1-100). Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / actionId / pattern
```
Added value: +"^([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})$"
```
- removedInput schema / properties / limit / $ref
```
Removed value: -"#/properties/pageSize"
```
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / limit / type
```
Added value: +"integer"
```

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / limit

Added value: +{
+  "$ref": "#/properties/pageSize",
+  "description": "The same setting as pageSize. Send either."
+}

AddedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the read-only/idempotent annotations by enumerating the event kinds, the shape of from/to values (user ids, channel arrays, page URLs), the three actor types (user, api_key, system), and the createdAt field. It also discloses the recording-start limitation and the nextCursor pagination contract. Minor gap: no indication of default page behavior or result volume beyond the schema default of 25.

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?

Front-loads the core purpose, then layers exclusion and pagination guidance in a logical order with no filler sentences. It is a dense run-on paragraph with parenthetical enumerations that could be broken into shorter clauses, but nothing is redundant.

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?

There is no output schema, and the description compensates fully by describing the event record shape (kind, from/to, actor, createdAt) and the exact kind values an agent will see. Combined with the history and pagination caveats, an agent has everything needed to call and interpret this tool correctly.

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 schema already documents actionId, limit, pageSize and cursor. The description only reinforces the cursor round-trip ('Pass nextCursor back as cursor'), and says nothing about the limit/pageSize aliasing that the schema flags. It adds a little meaning but the schema does the heavy lifting.

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 ('List who changed an action's title, owner, channels, description or published pages') plus ordering ('newest first'). The final sentences explicitly separate it from devtune_get_actions, so an agent can distinguish it from the sibling that returns lifecycle state.

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 an explicit exclusion ('Lifecycle moves such as accepting, going live or archiving are not events') and names the alternative to use instead ('read them from devtune_get_actions'). It also sets expectations about the window of available data ('History starts when recording began'), which tells the agent when this tool will not satisfy a request for older edits.

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?