Codex Control Plane MCP

Overview Schema Source Related Servers Discussions Admin

codex_unarchive_thread

Unarchives a previously archived Codex thread to make it active again. Poll for command status after submission.

Instructions

Unarchive a known Codex thread through the worker or app-server command lane. Use this only for an existing archived thread. Next poll codex_get_worker_command_status when commandId is returned.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "codex_unarchive_thread"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes
`project_id`	No
`timeout_seconds`	No
`refresh_catalog`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`agentGuidance`	No
`agentGuidanceText`	No
`recoveryAttemptState`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJun 19, 2026
- addedOutput schema / properties / agentGuidance
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
- addedOutput schema / properties / agentGuidanceText
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recoveryAttemptState
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
Addedv0.1.3Jun 18, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Describes the mechanism (worker or app-server command lane) and that it returns a commandId, but does not detail side effects, permissions, or state changes beyond 'unarchive'. With no annotations, more detail would be helpful.

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

Conciseness5/5

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

Two sentences that efficiently convey purpose, usage condition, and follow-up step. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core purpose and a follow-up step, but lacks details on parameter semantics and prerequisite conditions. Given the 4 parameters and no schema descriptions, more completeness would be warranted despite the presence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 4 parameters with 0% description coverage. The description does not explain any parameter beyond the core action, leaving timeout_seconds and refresh_catalog ambiguous. The parameter names provide some hints, but the description adds no value.

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?

The description clearly states the action (unarchive) and the resource (Codex thread), and the phrase 'known Codex thread' distinguishes it from similar tools like codex_archive_thread.

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

Usage Guidelines4/5

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

Explicitly states when to use (only for existing archived thread) and provides a next step (poll codex_get_worker_command_status). No explicit when-not-to-use, but the condition is implied.

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

Deploy Server