Skip to main content
Glama
Sign In

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Delivery status

delivery_status
Read-only

Where this workspace delivers drafts, plus whether a token for that provider is saved. Never returns the token. provider is github or sanity. For github: repo, branch, path template, body format, label and the frontmatter mapping; check is a live read of the repository and the branch with that token: ok plus permissions.push, or a reason (no-target, no-token, secrets-key-missing, github-unauthorized (GitHub rejected the token itself: wrong, cut short, expired or revoked), repo-not-found, branch-not-found, no-push, github-error). For sanity: label, the mapping of canonical fields to Sanity field names, and sanity with projectId, dataset, documentType, studioUrl, slugField, bodyField, languageField, dateType and tables; check is a count query of published documents of that type plus a dry-run write: ok, canWrite and documentCount, or a reason (no-target, no-token, secrets-key-missing, dataset-not-found, sanity-unauthorized, no-write, sanity-error). check is null when nothing is configured. Free to call.

Input 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, but the description adds substantial context beyond them: the token is never returned, and `check` performs a live call (GitHub repo read with the token, or a count query plus dry-run write for Sanity) with a full enumerated reason taxonomy (no-token, github-unauthorized, repo-not-found, no-write, etc.). It does not address the cost/latency of that live network call or the mild tension with openWorldHint=false.

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

Conciseness4/5

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

Front-loaded with the core answer, then per-provider detail; every clause carries information and there is no filler. The long semicolon-chained sentences are dense and hard to scan, but with no output schema the enumeration of return fields is doing necessary work.

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

Completeness5/5

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

There is no output schema, so the description must document return values itself — and it does, per provider, including the null case when nothing is configured and the exact error reasons for `check`. An agent has everything needed to interpret a response.

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?

Only one optional parameter, and the schema already documents it at 100% coverage, including the default-workspace fallback. The description adds no additional semantics about workspaceId, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource statement: it reports where the workspace delivers drafts and whether a provider token exists, then enumerates the exact fields returned per provider (repo/branch/path template for github; projectId/dataset/documentType for sanity). It distinguishes itself from the delivery action sibling (deliver_draft) by being a status/read tool, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated — the tool is a pre-flight/diagnostic read ('whether a token for that provider is saved', 'Free to call'), but it never says when to call it instead of deliver_draft, or that it should be called before delivery to diagnose a failure. 'Free to call' gives a cost hint but no exclusion criteria.

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