Skip to main content
Glama

integrations_set_auth

Set or update the authentication on an HTTP-API integration, generically. Identify it by integration_id or base_url. Pass auth = {type: bearer|api_key|basic|query|custom_headers|browser_identity|none, ...}: bearer/basic → {token}; api_key → {token, header_name?} (key rides in a HEADER); query → {token, param_name} (key rides in the QUERY STRING, e.g. param_name='api_key' → ?api_key=…); custom_headers → {headers:{name:value,...}}; browser_identity → {identity_id|identity_name, extract}; an extract block that echoes a percent-encoded cookie (Laravel's XSRF-TOKEN; a 419 means this) takes value_format:'urlencoded'. Token values are encrypted; nothing is stored in cleartext. To only refresh a browser_identity session, OMIT auth and pass cookies (and/or local_storage) — they are merged into the bound identity without touching its config. (oauth2 / service_account use the REST settings flow.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
authNoAuth to set: {type, token?, header_name?, headers?(object), identity_id?, identity_name?, extract?(object)}. Omit to only refresh cookies on an existing browser_identity integration. `token` also takes a `clip:` handle from clipboard.copy (a key someone sent in a chat, pattern 'api_key' or 'password'), with type bearer, api_key, basic or query: the key is set without anyone reading it.
cookiesNoCookies to merge into the bound browser identity. Each {name, value, domain?, path?, expires?}. Existing names are overwritten; new ones added.
base_urlNoOr the integration's base URL, e.g. https://api.boomnow.com.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
local_storageNolocalStorage entries to merge. Each {origin, name, value}.
integration_idNoIntegration id (from integrations.list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / auth / description
      Previous value: -"Auth to set: {type, token?, header_name?, headers?(object), identity_id?, identity_name?, extract?(object)}. Omit to only refresh cookies on an existing browser_identity integration."New value: +"Auth to set: {type, token?, header_name?, headers?(object), identity_id?, identity_name?, extract?(object)}. Omit to only refresh cookies on an existing browser_identity integration. `token` also takes a `clip:` handle from clipboard.copy (a key someone sent in a chat, pattern 'api_key' or 'password'), with type bearer, api_key, basic or query: the key is set without anyone reading it."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: token values are encrypted and nothing is stored in cleartext, cookie/local_storage values are merged into the bound identity without touching its config, and a 419 is diagnosed as an unencoded extract echo. These are exactly the operational facts an agent needs before a write call.

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-loaded with the action and identification, and no sentence is filler. However, it is a single dense block with nested parentheticals and semicolon-separated cases that is harder to scan than a short bulleted breakdown of auth types would be.

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?

Covers addressing, every supported auth type, the cookie-refresh-only path, encryption behavior, and the redirect for oauth2/service_account. With no output schema needed and a fully documented schema, nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description adds real meaning: the type-to-field pairing (bearer/basic → token, api_key → token+header_name, query → token+param_name), the header-vs-query-string distinction, and the value_format:'urlencoded' requirement for percent-encoded cookie echoes. This is semantics, not a restatement of 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 ('Set or update the authentication on an HTTP-API integration') and defines the two addressing modes (integration_id or base_url). It also carves out what it does not cover ('oauth2 / service_account use the REST settings flow'), so an agent can place it against auth-flow siblings.

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?

Explicit when-to-use paths: full auth config via `auth`, or refresh-only via omitting `auth` and passing `cookies`/`local_storage`. It names the excluded auth types and points to the alternative flow, leaving little to inference.

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.