Skip to main content
Glama

Get Magic Audience Video Upload Status

get_magic_audience_video_upload_status
Read-only

Get Meta video upload status for a Magic Audience video id. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "communityId": "<communityId>",
      "videoId": "<videoId>"
    },
    "name": "get_magic_audience_video_upload_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesUploaded video ID returned when the upload started.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / videoId / description
      Added value: +"Uploaded video ID returned when the upload started."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, closed-world operation, so the description does not need to restate safety. It adds meaningful behavioral context around business access gating, FREE-business exclusion, grace-period warnings, and blocking behavior. It does not describe return statuses or polling behavior, which keeps it from a 5.

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?

The purpose is front-loaded, followed by the access-gating constraints. The guidance is mostly purposeful, though it repeats the requirement to check access before collecting inputs and could be tightened into fewer sentences.

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

Completeness3/5

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

The description covers permission gating well, which is important for this tool. However, because there is no output schema, the definition should probably explain what upload statuses are returned or how to interpret them; it does not, leaving a meaningful gap for a status-retrieval tool.

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 description coverage is 100%, and both communityId and videoId are already documented in the input schema, including the instruction not to invent a community ID. The description only reinforces that the video ID is a Magic Audience video id, adding little beyond the schema baseline.

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 states a specific verb and resource: get Meta video upload status for a Magic Audience video id. It is clear enough to distinguish from upload-oriented siblings, but it does not explicitly contrast this status check with upload_magic_audience_video or other status tools.

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 definition gives explicit when-not-to-use rules: FREE businesses cannot use the tool regardless of feature rows, and blocked access must not proceed. It also names the required prerequisite tool, check_business_tool_access, and instructs the agent to surface grace-period warnings and a resubscribe link before continuing.

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.

Resources