Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Get next post to write

next_write
Read-only

Return the next post to write: the earliest-dated post whose status is scheduled. Posts with no date sort last. Statuses ready, writing and failed are never returned: ready already has a body, and list_posts returns those. Returns null when nothing is scheduled. Use the term it returns for the write pipeline. standard is the short form of the rules that block a draft, carried here because this is the call you make before the first sentence exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoThe workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "The workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds genuine behavioral detail: null is returned when nothing is scheduled, undated posts sort last, and three statuses are filtered out. The dangling clause about the 'standard' term being 'carried here' is opaque and slightly muddies rather than clarifies.

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

Conciseness3/5

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

The first four sentences are tight and front-loaded with the selection and null-return rules. The trailing sentences about 'the term it returns' and 'standard' are confusing, undefined, and appear to carry context that does not belong in a tool description.

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

Completeness4/5

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

For a one-optional-param read tool with no output schema and annotations covering safety, the description covers return semantics (null, sort order, filtered statuses) well. The ambiguous 'term'/'standard' passage is the only real gap in an otherwise sufficient definition.

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% and the single workspaceId parameter is fully documented in the schema, including its default behavior. The description adds no parameter-level information, so baseline 3 applies.

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+resource ('return the next post to write') and immediately defines the selection rule: the earliest-dated post whose status is scheduled, with undated posts sorting last. An agent can distinguish this from list_posts and get_post without opening the schema.

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 excludes statuses ready, writing and failed and reasons why, and routes the agent to list_posts for those. The final line implies this is the pre-writing call, but it never states a positive 'use this when you are about to start drafting' instruction outright.

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

All seodraft toolsInspect
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