Retrieve a draft post's full content by ID, returning title, body, and metadata.
Get the full content of a draft post by ID. Returns title, body, metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| draft_id | Yes | The draft ID to retrieve |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| body | No | ||
| title | No | ||
| audience | No | ||
| subtitle | No | ||
| created_at | No | ||
| updated_at | No | ||
| word_count | No |
Changes observed during successful MCP inspections.
Input schema / properties / draft_id / exclusiveMinimumAdded value: +0Input schema / properties / draft_id / maximumAdded value: +9007199254740991Input schema / properties / draft_id / typePrevious value: -"number"New value: +"integer"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "audience": {
+ "$ref": "#/properties/title"
+ },
+ "body": {
+ "$ref": "#/properties/title"
+ },
+ "created_at": {
+ "$ref": "#/properties/title"
+ },
+ "id": {
+ "exclusiveMinimum": 0,
+ "maximum": 9007199254740991,
+ "type": "integer"
+ },
+ "subtitle": {
+ "$ref": "#/properties/title"
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "updated_at": {
+ "$ref": "#/properties/title"
+ },
+ "word_count": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "id"
+ ],
+ "type": "object"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description's 'Get' is consistent with that. The description adds limited behavioral context by mentioning return contents, but it does not disclose behavior for missing drafts, authorization needs, or any additional side effects. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one concise sentence with no wasted words. It front-loads the verb and resource, then provides the useful scope ('full content') and return fields, making it easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one fully documented required parameter and an output schema present, the description is almost complete. It lacks an explicit pointer about when to choose this over closely related siblings like export_draft or list_drafts, but that gap is minor given the clarity of the rest.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% description coverage for the single parameter, already stating 'The draft ID to retrieve'. The description's 'by ID' adds no new semantic meaning beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific verb ('Get'), resource ('draft post'), and selection criterion ('by ID'), and further specifies 'full content' with return fields ('title, body, metadata'). This distinguishes it from siblings like list_drafts, get_post, and export_draft.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool: when the agent has a draft_id and needs the full content of a specific draft. However, it does not explicitly name alternatives or exclusions, such as when to prefer list_drafts or export_draft, so guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.