Skip to main content
Glama
lindoai

mcp-lindoai

Official

Check Page Creation Status

check_page_status
Read-only

Poll the status of a page-creation workflow by providing the workflow_id; call repeatedly until done is true and status is complete or errored.

Instructions

Poll the status of a page-creation workflow started by create_page. Pass the workflow_id you received from that tool. While running, call this again after poll_after_ms ms. Once done is true, status is complete or errored; when complete, result holds the published page info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow id returned by create_page

Implementation Reference

  • Registration of the 'check_page_status' tool using server.registerTool with the name 'check_page_status'.
    server.registerTool(
      "check_page_status",
      {
        title: "Check Page Creation Status",
        description: "Poll the status of a page-creation workflow started by `create_page`. Pass the `workflow_id` you received from that tool. While running, call this again after `poll_after_ms` ms. Once `done` is true, `status` is `complete` or `errored`; when complete, `result` holds the published page info.",
        inputSchema: {
        workflow_id: z.string().describe("Workflow id returned by create_page"),
      },
        annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      },
      async ({ workflow_id }) => {
        const data = await apiCall(`/v1/ai/workspace/page/status/${encodeURIComponent(workflow_id)}`, "GET");
        const payload = data?.result || data;
        return { content: [{ type: "text", text: JSON.stringify(payload, null, 2) }] };
      }
    );
  • Handler function that accepts workflow_id, calls the API endpoint /v1/ai/workspace/page/status/{workflow_id}, and returns the result as text content.
    async ({ workflow_id }) => {
      const data = await apiCall(`/v1/ai/workspace/page/status/${encodeURIComponent(workflow_id)}`, "GET");
      const payload = data?.result || data;
      return { content: [{ type: "text", text: JSON.stringify(payload, null, 2) }] };
    }
  • Input schema for check_page_status: requires workflow_id (string) described as 'Workflow id returned by create_page'.
      inputSchema: {
      workflow_id: z.string().describe("Workflow id returned by create_page"),
    },
  • The apiCall helper function used by the handler to make HTTP requests to the Lindo API.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior5/5

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

Annotations indicate read-only and non-destructive behavior. The description adds details about polling semantics, states (running, complete, errored), and the `result` field. There is 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.

Conciseness5/5

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

Three sentences, no redundant information. Front-loaded with purpose, followed by usage and state explanation. Every sentence adds value.

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?

Despite no output schema, the description explains all return fields (`done`, `status`, `result`) and provides a complete polling protocol. The tool is simple with one parameter, and the description is fully adequate.

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

Parameters4/5

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

Schema coverage is 100% with a clear description for `workflow_id`. The description adds context by specifying its source (`create_page`) and usage pattern, slightly exceeding schema-only information.

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 tool polls the status of a page-creation workflow started by `create_page`. It uses a specific verb ('poll') and resource ('page-creation workflow'), and distinguishes from sibling tools like `check_blog_status` or `check_website_status` by tying it to `create_page`.

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

Usage Guidelines5/5

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

The description provides explicit instructions: pass the `workflow_id` from `create_page`, poll after `poll_after_ms` ms, and interpret `done`, `status`, and `result` fields. It implicitly tells when not to use (only for workflows from `create_page`).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lindoai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server