Skip to main content
Glama

Update Clerk application

update_application

Rename an application in the connected workspace. The name appears on sign-in screens and in emails. Only the name can be changed; billing plans and add-ons are not supported. Returns the updated application with its instances and publishable keys; secret keys are removed.

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>",
      "name": "<name>"
    },
    "name": "update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew name for the application.
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
nameYes
instancesYes
application_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly=false and destructive=false; the description adds real value on top by disclosing the user-visible blast radius (sign-in screens, emails), that no other fields are affected, and that secret keys are stripped from the return payload. The return-shape sentence partly duplicates the output schema, but the security note about secret keys is information not present in structured fields.

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, then the constraint, then the return contract. Every sentence supplies distinct information and there is no filler.

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 small two-parameter mutation with annotations and an output schema, the description covers scope, side effects, and the security-relevant return detail. It omits any mention of permission/auth requirements or error conditions, which keeps it from a 5.

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 both parameters are already documented in the schema; the description adds only the meaning of 'name' (rendered on sign-in screens and emails) and says nothing extra about application_id. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource ('Rename an application') plus the scope ('in the connected workspace'), and clarifies that only the name field is mutable, which separates it from broader update/patch tools in the sibling set. It does not name any sibling as an alternative, which keeps it just below a 5.

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 clear context for use (renaming an application whose name appears on sign-in screens and in emails) and an explicit exclusion ('billing plans and add-ons are not supported'). It stops short of routing to alternative tools, so it lacks the when-not/use-instead pairing a 5 would require.

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