Skip to main content
Glama

Get Business Video Presigned URL

get_community_video_presigned_url
Read-only

Get a signed PUT URL for uploading a community video. Business and community refer to the same thing and are interchangeable. 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>",
      "originalname": "<originalname>",
      "mimetype": "<mimetype>"
    },
    "name": "get_community_video_presigned_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityIdNo
mailTypeNoEmail template type to read or update.
mimetypeYesMIME type of the file; use one of the allowed values.
entityTypeNoType of product or entity this action targets.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
checkpointIdNoChallenge checkpoint ID, from the challenge checkpoint list.
originalnameYesOriginal file name of the upload.
participantIdNoChallenge participant ID, from a challenge participant listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / checkpointId / description
      Added value: +"Challenge checkpoint ID, from the challenge checkpoint list."
    • 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 / entityType / description
      Added value: +"Type of product or entity this action targets."
    • addedInput schema / properties / mailType / description
      Added value: +"Email template type to read or update."
    • addedInput schema / properties / mimetype / description
      Added value: +"MIME type of the file; use one of the allowed values."
    • addedInput schema / properties / originalname / description
      Added value: +"Original file name of the upload."
    • addedInput schema / properties / participantId / description
      Added value: +"Challenge participant ID, from a challenge participant listing."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive, closed-world call, which is consistent with merely minting a URL; the description adds substantial hidden behavior the annotations cannot convey, namely the hard permission gate, the FREE-tier block, and the grace-period warning flow. It stops short of stating the URL's lifetime or any required PUT headers (Content-Type matching mimetype), which would matter for actually completing the upload.

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?

Front-loads the core action in the first sentence and then sequences the access-check preconditions logically. The repeated emphasis on access blocking is deliberate rather than redundant, though it could be tightened into one precondition sentence.

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

Completeness4/5

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

With eight parameters at 88% coverage and no output schema, the definition covers the risky part (permission gating) thoroughly, and the return is implied by "signed PUT URL". What is missing is how to consume the returned URL safely and whether it expires, which an agent would otherwise have to guess.

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 88%, so the schema already documents communityId provenance, mimetype's enum, and originalname. The description adds no parameter-level meaning beyond that baseline, and the required trio of communityId/originalname/mimetype is not called out in prose, though the schema carries it adequately.

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?

States a specific verb and resource ("Get a signed PUT URL for uploading a community video") and immediately disambiguates it from the get_business_video_presigned_url sibling by declaring business and community are interchangeable terms. An agent can identify the operation and its near-duplicate without opening either schema.

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?

Gives explicit preconditions and exclusions: call check_business_tool_access before collecting inputs, FREE businesses cannot use it regardless of feature rows, show the grace-period warning and verified resubscribe link, and never proceed when access is blocked. Both the when-to-use path and the when-not-to-use conditions are named.

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