Skip to main content
Glama

Show my webhook inbox pro settings

inbox_pro_get
Read-only

Show your webhook inbox pro settings: the upgraded inbox, forwarding (with counts), signature preset and handshakes. Secrets are never shown. instance_id is the pro plan's (ipr_...), not the inbox's. inbox_pro_set changes them. Works after the plan ended too.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "ipr_exampleexampleexample2"
    },
    "name": "inbox_pro_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "ipr_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: secrets are redacted from the response, forwarding values come with counts, and the call still succeeds after plan expiry. It does not discuss pagination or response shape, but for a settings read that is minor.

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 what is shown, then tacks on the parameter quirk, the setter alternative, and the lifecycle note — each sentence carries distinct information. The clipped, fragmentary style ('Works after the plan ended too.') is dense but readable; a slightly more structured layout would read better without adding length.

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?

There is no output schema, and the description compensates by enumerating the returned fields and stating the redaction rule. Combined with the read-only annotations and the named mutating sibling, an agent has everything needed to decide to call it, pick the right id, and interpret the result.

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%, so baseline is 3, but the description earns above baseline by disambiguating the required parameter: 'instance_id is the pro plan's (ipr_...), not the inbox's'. That corrects a likely confusion the schema text ('Utility instance id from buy or list_utilities') does not resolve, and the ipr_ prefix is echoed in the schema example.

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 ('Show') and resource ('webhook inbox pro settings') and then enumerates the actual contents returned: the upgraded inbox, forwarding with counts, signature preset and handshakes. It also names the sibling that performs the mutation (inbox_pro_set), so an agent can separate read from write 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the mutation case to inbox_pro_set ('inbox_pro_set changes them') and adds a lifecycle condition ('Works after the plan ended too'), which tells the agent this remains callable on lapsed plans. It does not spell out a when-not-to-use case beyond that, so it falls short of full routing guidance.

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.