Skip to main content
Glama

get_status

Check the processing status and progress percentage of a short video creation request by providing the request ID.

Instructions

Check processing status and progress of a short creation request. Returns status (queued/processing/completed/failed), progress percentage, and current step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYesThe request ID from create_short (24-char hex)

Implementation Reference

  • The tool handler logic for 'get_status' which calls the Ssemble API client.
    async ({ requestId }) => {
      try {
        const result = await client.getStatus(requestId);
        return { content: [{ type: 'text', text: formatStatusResponse(result) }] };
      } catch (error) {
        return { content: [{ type: 'text', text: formatError(error) }], isError: true };
      }
    }
  • The registration function for the 'get_status' tool.
    export function registerGetStatus(server, client) {
      server.tool(
        'get_status',
        'Check processing status and progress of a short creation request. Returns status (queued/processing/completed/failed), progress percentage, and current step.',
        schema,
        async ({ requestId }) => {
          try {
            const result = await client.getStatus(requestId);
            return { content: [{ type: 'text', text: formatStatusResponse(result) }] };
          } catch (error) {
            return { content: [{ type: 'text', text: formatError(error) }], isError: true };
          }
        }
      );
    }
  • Input validation schema for the 'get_status' tool.
    const schema = {
      requestId: z.string().regex(/^[0-9a-fA-F]{24}$/).describe('The request ID from create_short (24-char hex)'),
    };
  • The underlying API client method that performs the actual network request for 'get_status'.
    // Endpoint 3: GET /shorts/:id/status
    async getStatus(requestId) {
      return this._request('GET', `/shorts/${requestId}/status`);
    }
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses return structure comprehensively: enumerates status values (queued/processing/completed/failed), mentions progress percentage and current step. Missing error behavior (e.g., invalid requestId) and read-only nature, but effectively compensates for absent output schema.

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?

Two sentences with zero waste. First sentence defines action and scope; second sentence discloses return values. Front-loaded with essential information, no redundant phrases.

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?

Appropriate for tool complexity (single param, 100% schema coverage, simple behavior). Description adequately compensates for missing output schema by detailing return structure. Links to sibling create_short via 'short creation request' context, completing the operational picture.

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 coverage is 100% with requestId fully documented (type, pattern, description linking to create_short). Description does not mention parameters, but baseline of 3 is appropriate when schema documentation is complete; no additional parameter semantics needed in description.

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?

Clear specific verb 'Check' with explicit resource 'processing status and progress of a short creation request'. Distinguishes from sibling get_shorts (which returns content) and list_requests (which lists multiple) by focusing on detailed progress polling of a single creation job.

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?

Implies usage context by referencing 'short creation request' and status lifecycle (queued/processing/completed/failed), suggesting polling workflow after create_short. Lacks explicit 'when to use vs alternatives' statement (e.g., contrasting with list_requests), but context is clear from description and parameter schema reference to create_short.

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/ssembleinc/ssemble-mcp-server'

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