devtune_get_action_brief
Get the stored brief for a specific action, including readiness status, whether research was cut short, settled credits used, generated timestamp, and the brief when one is ready. briefFormat 2 briefs return briefMarkdown (the brief, then an Evidence section that is context, not specification) plus the structured brief (task, outline, facts with sources, each project or external fact carrying sourceRef, the supplied project data ref or source packet URL it restates, and sections, the zero-based indexes of the outline sections that use it; briefs written before refs or sections omit them; leaveOut, rules, doneWhen) and evidence objects; a draft states only product facts on the facts list. The optional inboundLinkPlan names up to three related-page edits with source sections, excerpts, suggested anchors, a target and a pinned crawl generation. edgeStatus not_observed_in_generation is a suggestion based on that generation, not a measured missing or live link. Current locked or retiring source and target pages have their edits removed on read. Stale or unverifiable current brief inputs omit the plan while preserving the stored target brief. The single-page drafter leaves related edits outstanding for human approval and a fresh crawl. briefFormat 1 briefs return Markdown only and cannot be drafted from until regenerated. When claim checks are enabled for the project and one has run, claimCheck reports how the brief's facts (or, for a format 1 brief, its claim references) held up against the project's owned content, searched for each claim: coverage (claims checked, claims whose owned-content search failed, and claims set aside by source type) and a judgment per claim with its source (a site page with its URL, the project profile, DevTune's own analysis, an external source, or general knowledge), the pages a claim that is not supported was judged against and the quoted passage for a confirmed contradiction. It annotates the brief and never changes it. robotsTxtDraft carries the action's drafted robots.txt edit, or null: per robots.txt file, the edited file and a unified diff (at most 16 KB) that add only the narrowest Allow rules, drafted from the file the audit read, or a no_change or unavailable status with its reason. An allow with match exact_page opens only that sampled page, not everything the blocking rule covers; widening it is the customer's call. A sampled page that redirects is never drafted, its first hop included: it is listed in skipped with reason redirected and the sampled page URL. Every read re-checks a stored draft against the current acknowledgements and primary domains: it comes back unavailable with reason out_of_date when it would change an acknowledged URL, check_unavailable when that check could not run (try again), too_large_to_check when it is too large to check, or an ownership reason when its host is not itself a primary domain (ownership is exact-host only). A robots.txt reached through a redirect, from either side, is never drafted (robots_redirected). If the project has any acknowledged restriction for a crawler scope, no edit is drafted or shown for that crawler (acknowledged_scope). A human applies it.
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_brief"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actionId | Yes | UUID of the action to load the brief for. |