Action Brief Generation via API and MCP

Trigger Action Brief Generation Programmatically

You can now request a command-center brief for a specific action without going through the web app. DevTune now supports manual brief generation from both the public REST API and the MCP server.

REST API

Use POST /api/v2/projects/{projectId}/actions/{actionId}/brief to queue or reuse brief generation for a project action.

What the Endpoint Returns

• ready when the brief already exists and can be used immediately
• queued when generation has been queued in the background
• generating when a generation job is already in progress

Required Scope

API keys must include the actions.write scope to call the new mutation endpoint.

MCP Server

The public MCP server now includes a new devtune_generate_action_brief tool. Give it an actionId and DevTune will return the same generation state you get from the REST API.

Typical Use Cases

• Trigger an execution brief for a recommended action from an AI assistant
• Kick off brief generation from an internal automation or agent workflow
• Check whether a brief is already ready before opening it in a downstream tool

Read + Write Flow

You can combine the new mutation with the existing devtune_get_action_brief tool or GET /api/v2/projects/{projectId}/actions/{actionId}/brief endpoint to trigger generation first and then read back the stored brief once it is ready.