Skip to main content
Glama

Publish a workflow as a REST API

writ_expose_workflow_api
Idempotent

Publishes a saved workflow as a REST endpoint (a POST URL that waits and returns its JSON). Repeated calls reuse it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_expose_workflow_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
workflowNo
workflow_idNo
wait_timeoutNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / timeout_seconds
      Added value: +{
      +  "maximum": 300,
      +  "minimum": 5,
      +  "type": "integer"
      +}
    • addedInput schema / properties / wait_timeout
      Added value: +{
      +  "maximum": 300,
      +  "minimum": 5,
      +  "type": "integer"
      +}
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / label / description
      Removed value: -"Optional name for the endpoint."
    • removedInput schema / properties / timeout_seconds
      Removed value: -{
      -  "description": "Managed run timeout. Defaults to 120, or 300 for AI navigation workflows.",
      -  "maximum": 300,
      -  "minimum": 5,
      -  "type": "integer"
      -}
    • removedInput schema / properties / wait_timeout
      Removed value: -{
      -  "description": "Deprecated alias of timeout_seconds.",
      -  "maximum": 300,
      -  "minimum": 5,
      -  "type": "integer"
      -}
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, and the description usefully corroborates idempotency ("repeated calls reuse it") while explaining that the endpoint blocks and returns JSON. That is genuine value beyond the annotations. It still omits what happens if a workflow is already published, whether an existing endpoint can be overwritten, and whether authentication or a public URL is involved.

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence is slightly ambiguous — "reuse it" could refer to the workflow or the published endpoint — so it is efficient but not perfectly precise.

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

Completeness2/5

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

This is a publishing/mutation-style tool with five parameters at 0% schema coverage, no output schema, and zero required fields, so the description carries most of the explanatory burden. It explains the endpoint concept but leaves the parameter set, the publish/republish lifecycle, and the error surface unexplained, which is inadequate for this complexity.

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 description coverage is 0% across five undocumented, all-optional parameters. The description says nothing about label, workflow vs workflow_id (mutually exclusive alternatives?), and critically does not distinguish wait_timeout from timeout_seconds, which both take integers from 5 to 300 and are otherwise indistinguishable. The only implicit link is "waits" hinting at wait_timeout, which is not enough for an agent to set values confidently.

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?

The description gives a specific verb and resource ("Publishes a saved workflow as a REST endpoint") and adds a clarifying detail that the endpoint is a POST URL which waits and returns JSON. That is enough for an agent to know what the tool produces. It does not, however, distinguish the tool from siblings such as writ_run_workflow or writ_website_to_api, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to choose this tool over writ_run_workflow or writ_website_to_api, nor any prerequisites (does the workflow need to exist and be saved first?). "Repeated calls reuse it" is a behavioral note about idempotency, not selection guidance. The agent has to infer usage entirely from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.