Skip to main content
Glama

Create redirect URL

create_redirect_url

Allowlist a redirect URL on an instance for SSO in a mobile or desktop application. Supports HTTPS URLs and custom schemes such as my-app://oauth-callback. Returns the created redirect URL object. An already allowlisted URL returns an error.

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": {
      "application_id": "<application_id>",
      "instance": "<instance>",
      "url": "<url>"
    },
    "name": "create_redirect_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRedirect URL to allowlist, such as my-app://oauth-callback.
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare write, non-destructive, non-idempotent, closed-world, so the description adds real value on top: allowed URL schemes, that the created object is returned, and that an already-allowlisted URL errors out, which confirms the non-idempotent hint. It does not mention permission requirements or whether the allowlisting can be undone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and purpose, then supported schemes, then return/error behavior. No filler or redundancy.

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?

An output schema exists, so return values need only a passing mention, and the description still names the returned object and the duplicate-error case. The remaining gap is auth/permission requirements for allowlisting a redirect URL in a production instance, which an agent might need before calling.

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 100%, so all three parameters (application_id, instance, url) are already documented in the schema, down to the app_/ins_ prefixes and the development/production instance values. The description only restates the URL scheme examples already present in the schema, so it meets the baseline without adding meaning.

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 (allowlist/create a redirect URL), the resource, and the reason (SSO for mobile or desktop apps). The 'allowlist' framing plus the duplicate-URL note makes the operation distinguishable from the list_redirect_urls sibling 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?

Gives a clear usage context: SSO in a mobile or desktop application, with supported URL forms (HTTPS and custom schemes). It does not say when to use this versus alternatives or what prerequisites/permissions are required, so it falls short of full routing guidance but the context is unambiguous.

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