Skip to main content
Glama

threads_get_container_status

Check the processing status of a Threads media container to monitor upload progress and verify completion.

Instructions

Check the processing status of a Threads media container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
container_idYesContainer ID to check

Implementation Reference

  • Registration and handler implementation for the threads_get_container_status tool.
    server.tool(
      "threads_get_container_status",
      "Check the processing status of a Threads media container.",
      {
        container_id: z.string().describe("Container ID to check"),
      },
      async ({ container_id }) => {
        try {
          const { data, rateLimit } = await client.threads("GET", `/${container_id}`, {
            fields: "id,status,error_message",
          });
          return { content: [{ type: "text", text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text", text: `Get container status failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'processing status' but fails to detail what that entails (e.g., stages like pending, completed, failed), whether it's a read-only operation, potential rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that likely returns status information. It doesn't explain what the status output includes (e.g., success indicators, error messages), leaving the agent uncertain about the tool's full context and expected behavior.

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?

The schema description coverage is 100%, with the parameter 'container_id' fully documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline score of 3 where the schema handles parameter documentation adequately.

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 clearly states the tool's purpose with a specific verb ('Check') and resource ('processing status of a Threads media container'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from the sibling tool 'ig_get_container_status' (which appears to serve a similar function for Instagram), so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives, such as the sibling 'ig_get_container_status' or other status-checking tools. It lacks context about prerequisites, timing, or any exclusions, leaving the agent with minimal usage direction.

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/mikusnuz/meta-mcp'

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