Skip to main content
Glama

Toggle Magic Content Subtitle

toggle_magic_content_subtitle

Enable or disable subtitles on a Magic Content asset. 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>",
      "assetId": "<assetId>",
      "subtitleEnabled": "<subtitleEnabled>"
    },
    "name": "toggle_magic_content_subtitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesCreative asset or Magic Content asset ID.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
subtitleEnabledYesWhether subtitles are shown on the video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / assetId / description
      Added value: +"Creative asset or Magic Content asset ID."
    • 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 / subtitleEnabled / description
      Added value: +"Whether subtitles are shown on the video."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, closed-world mutation; the description adds substantial context beyond that about entitlement gating, grace-period messaging, and blocked states. It stops short of describing the effect of disabling subtitles (whether existing caption data is lost or merely hidden), which would complete the mutation picture.

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 action in the first sentence, then sequences the prerequisite checks in execution order, which is easy for an agent to follow. It is somewhat instruction-dense for a three-parameter toggle, but every sentence carries a distinct precondition rather than padding.

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?

For a simple three-required-parameter mutation with full schema coverage and no output schema, the description covers the risky part well: entitlement checks and blocked-access behavior. Only the post-toggle state (what happens to existing subtitle data) is left unspecified.

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%, with assetId, communityId, and subtitleEnabled each documented in the schema itself, including the warning not to invent a communityId. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

Opens with a specific verb and resource: 'Enable or disable subtitles on a Magic Content asset,' which tells an agent exactly what state change results. It does not explicitly contrast itself with edit_magic_content or get_magic_content_settings, so the sibling differentiation is only implied by the narrow subtitle scope.

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 ordering: check business permissions, call check_business_tool_access before collecting inputs, surface grace-period warnings and the resubscribe link, and never proceed when access is blocked. It also states a hard exclusion (FREE businesses cannot use this tool regardless of individual feature rows), which is exactly the when-not guidance an agent needs.

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