Skip to main content
Glama

Patch MCP

set_call_visibility

DestructiveIdempotent

Make a call owned by the authenticated user public or private. Calls are private by default. Only publish when the user explicitly asks: a public call exposes its objective, phone numbers, transcript, result and audio to anyone with its permanent, token-free listen_url, including live audio while in progress. Set is_public to false to disable token-free access again; existing private signed links remain valid until they expire. Public visitors cannot stop the call or change visibility.

Input Schema

NameRequiredDescriptionDefault
call_idYesThe id of a call owned by this account.
is_publicYestrue publishes the call; false makes it private again.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "call_id": {
      -        "description": "Call identifier used with get_call, end_call and set_call_visibility.",
      -        "type": "string"
      -      },
      -      "is_public": {
      -        "description": "Updated visibility; public links expose call data.",
      -        "type": "boolean"
      -      },
      -      "listen_url": {
      -        "description": "URL for the user to listen, read the transcript and stop an active call.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "call_id",
      -      "is_public",
      -      "listen_url"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "error": {
      -        "description": "Machine-readable failure code.",
      -        "type": "string"
      -      },
      -      "message": {
      -        "description": "Explanation or recovery guidance.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "error"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "call_id": {
      +        "description": "Call identifier used with get_call, end_call and set_call_visibility.",
      +        "type": "string"
      +      },
      +      "is_public": {
      +        "description": "Updated visibility; public links expose call data.",
      +        "type": "boolean"
      +      },
      +      "listen_url": {
      +        "description": "URL for the user to listen, read the transcript and stop an active call.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "call_id",
      +      "is_public",
      +      "listen_url"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "error": {
      +        "description": "Machine-readable failure code.",
      +        "type": "string"
      +      },
      +      "message": {
      +        "description": "Explanation or recovery guidance.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "error"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "next_action": {
      +        "type": "string"
      +      },
      +      "operation_id": {
      +        "type": "string"
      +      },
      +      "status": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "operation_id",
      +      "status"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "properties": {
      +        "call_id": {
      +          "description": "Call identifier used with get_call, end_call and set_call_visibility.",
      +          "type": "string"
      +        },
      +        "is_public": {
      +          "description": "Updated visibility; public links expose call data.",
      +          "type": "boolean"
      +        },
      +        "listen_url": {
      +          "description": "URL for the user to listen, read the transcript and stop an active call.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "call_id",
      +        "is_public",
      +        "listen_url"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "additionalProperties": {},
      +      "properties": {
      +        "error": {
      +          "description": "Machine-readable failure code.",
      +          "type": "string"
      +        },
      +        "message": {
      +          "description": "Explanation or recovery guidance.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "error"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "description": "Successful result or a machine-readable tool error.",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations by naming exactly what becomes exposed (objective, phone numbers, transcript, result, audio, live audio), through what mechanism (permanent token-free listen_url), and what is and isn't reversible (signed links stay valid until expiry; public visitors cannot stop the call or change visibility). This is the security context the annotations alone cannot convey.

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, then layers the risk rationale and reversal behavior; nearly every sentence carries weight. It is on the longer side for a two-parameter tool, with minor repetition between 'private by default' and 'only publish when the user explicitly asks'.

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?

An output schema exists and parameters are fully documented, so the description's remaining burden is side-effect disclosure, which it covers thoroughly: exposure surface, default state, reversibility, link expiry, and what public visitors cannot do. Nothing needed to call this safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already defines both parameters, so the description adds only modest value: it reinforces ownership scoping on call_id and clarifies that is_public=false removes token-free access while leaving existing signed links untouched. Slightly above baseline but largely redundant with the schema.

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 ('Make a call ... public or private') and scopes it to calls 'owned by the authenticated user'. An agent can immediately tell this is a per-call visibility toggle, distinct from call lifecycle siblings like end_call or get_call.

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 an explicit when-to-use rule plus an exclusion: 'Only publish when the user explicitly asks', with the default state ('Calls are private by default') spelled out. It also tells the agent how to reverse the decision by setting is_public to false.

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