Skip to main content
Glama

Reauthorize a connector

reauthorize_connector
Idempotent

Renew the authorization of an organization connector that signs in to a provider in a browser, either an OAuth connector or a Composio-managed one, for a connector whose grant the provider revoked or whose first authorization never finished. This tool does not return the provider's address. Say plainly in reason why the sign-in is needed. The answer carries a request whose url the person opens, signed in to Valet, to sign in to the provider from there; give the person the url, then follow the request with get_request. The connector keeps its name and configuration, and only new tokens are issued. A repeat by the same person returns the same pending request. The request completes only after a new consent for an OAuth connector; for a managed toolkit an active connection is reused. A connector whose credential is a secret is refused, and the answer names the organization secrets it reads. A person sets those at organization scope, on the dashboard or with valet env set --org in their own terminal; set_env_vars sets one app's or agent's own variables and does not repair an organization connector. A Composio toolkit that takes an API key hands off to the Integrations page. Requires connecting a Valet account.

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": {
      "connector": "<connector>"
    },
    "name": "reauthorize_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoShown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The Linear sign-in expired. Sign in again so the agent can read tickets.
org_nameNoThe Valet organization the connector belongs to. Omit to use the organization the account joined first.
connectorYesThe connector to sign in again, by the name list_connectors shows.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
urlNoThe Integrations page the person opens. It holds no credential. Absent unless step is set.
stepNoWhat the person does on the Integrations page, for a Composio toolkit that takes an API key. Absent otherwise.
requestNoThe request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person.
secretsNoNames of the organization secrets the connector reads, which a person sets at organization scope on the dashboard or with valet env set --org. Never values. Absent for a connector that takes none.
connectorYesName of the connector to reauthorize.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."New value: +"Shown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."
  2. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."New value: +"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."
  3. Changed2 schema fields changed
    • changedInput schema / properties / connector / description
      Previous value: -"The connector's name in the organization."New value: +"The connector to sign in again, by the name list_connectors shows."
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The Linear sign-in expired. Sign in again so the agent can read tickets. Needed when the connector signs in to a provider."New value: +"Why the request is made, in the words the person reads on the request page, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."
  4. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Needed when the connector signs in to a provider. Why the request is made, in the words the person reads on the request page, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."New value: +"Why the request is made, in the words the person reads on the request page, such as: The Linear sign-in expired. Sign in again so the agent can read tickets. Needed when the connector signs in to a provider."
  5. Changed1 schema field changed
    • changedOutput schema / properties / secrets / description
      Previous value: -"Names of the secrets the connector reads, which set_env_vars sets. Never values. Absent for a connector that takes none."New value: +"Names of the organization secrets the connector reads, which a person sets at organization scope on the dashboard or with valet env set --org. Never values. Absent for a connector that takes none."
  6. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Needed when the connector signs in to a provider. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."New value: +"Needed when the connector signs in to a provider. Why the request is made, in the words the person reads on the request page, such as: The Linear sign-in expired. Sign in again so the agent can read tickets."
  7. Changed1 schema field changed
    • changedOutput schema / properties / secrets / description
      Previous value: -"Names of the secrets a secret-credential connector reads."New value: +"Names of the secrets the connector reads, which set_env_vars sets. Never values. Absent for a connector that takes none."
  8. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Needed when the connector signs in to a provider. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."New value: +"Needed when the connector signs in to a provider. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."
  9. Changed3 schema fields changed
    • changedInput schema / properties / connector / description
      Previous value: -"Required. The connector's name in the organization."New value: +"The connector's name in the organization."
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Needed when the connector signs in to a provider. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key.",
      +  "maxLength": 280,
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "connector": {
      +      "description": "Name of the connector to reauthorize.",
      +      "type": "string"
      +    },
      +    "org": {
      +      "description": "Name of the Valet organization the call acted in.",
      +      "type": "string"
      +    },
      +    "request": {
      +      "additionalProperties": false,
      +      "description": "The request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person.",
      +      "properties": {
      +        "expires_at": {
      +          "description": "When the request expires unanswered, as an RFC 3339 UTC time.",
      +          "type": "string"
      +        },
      +        "fields": {
      +          "description": "Names of what the person enters, never values.",
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": [
      +            "null",
      +            "array"
      +          ]
      +        },
      +        "id": {
      +          "description": "Id of the request. Pass it to get_request to follow the request.",
      +          "type": "string"
      +        },
      +        "next_step": {
      +          "description": "What to do next: give the person the url, then follow the request with get_request.",
      +          "type": "string"
      +        },
      +        "url": {
      +          "description": "Dashboard page to give the person. They open it signed in to Valet to complete the request. It holds no credential.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "url",
      +        "expires_at",
      +        "fields",
      +        "next_step"
      +      ],
      +      "type": [
      +        "null",
      +        "object"
      +      ]
      +    },
      +    "secrets": {
      +      "description": "Names of the secrets a secret-credential connector reads.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "step": {
      +      "description": "What the person does on the Integrations page, for a Composio toolkit that takes an API key. Absent otherwise.",
      +      "type": "string"
      +    },
      +    "url": {
      +      "description": "The Integrations page the person opens. It holds no credential. Absent unless step is set.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "connector"
      +  ],
      +  "type": "object"
      +}
  10. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses that the tool does not return the provider address, that a pending request with a url is returned, that the connector keeps its name and configuration with only new tokens issued, that repeats return the same pending request, and that the call requires a connected Valet account. It does not discuss timing or expiry of the pending request, which is the main remaining behavioral gap.

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?

The purpose and scope are front-loaded in the first sentence, and each following sentence carries operational information rather than filler. It is dense and clause-heavy, though, which makes some sentences harder to parse than necessary, and the trailing 'Requires connecting a Valet account' is tacked on at the end.

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?

For a mutation tool with an output schema present, the description covers the authorization path, the pending-request handoff and its follow-up tool, the refusal case, and the account prerequisite. Nothing an agent needs to invoke it correctly and route the result is missing.

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%, so all three parameters are already documented, including reason, org_name defaulting, and connector naming. The description only adds an instruction about tone ('Say plainly in reason why the sign-in is needed'), which is marginal beyond the schema's own wording.

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 ('Renew the authorization of an organization connector') and narrows the scope to browser sign-in providers, OAuth or Composio-managed, whose grant was revoked or never completed. That scope distinguishes it from sibling attach/create connector operations without the agent needing to open another schema.

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 when-to-use conditions (revoked grant, unfinished first authorization), explicit when-not cases (secret-credential connectors are refused; Composio toolkits taking an API key hand off to the Integrations page), and a redirect for the confusable set_env_vars path. It also prescribes the follow-up step: return the url to the person, then call get_request.

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