Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Forget a browser session

jira_logout
Destructive

Delete stored browser-session cookies for a Jira instance, and optionally wipe its dedicated browser profile so the identity provider prompts for credentials again.

Instructions

Delete the stored browser-session cookies of an instance. With forgetBrowserProfile=true also wipes the dedicated browser profile, so the identity provider asks for credentials again.

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": "jira_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.
forgetBrowserProfileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description goes further by naming exactly what is destroyed (stored browser-session cookies) and the user-visible consequence of forgetBrowserProfile=true (profile wiped, identity provider re-prompts for credentials). It stops short of saying whether this affects only the local session or also invalidates tokens server-side.

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?

Two sentences, zero filler, with the primary effect front-loaded and the conditional flag behavior second. Every clause carries information an agent needs.

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 two-parameter destructive tool with no output schema, the description covers both parameters' effects and the post-condition (re-authentication required). It would be complete with a note on default flag behavior and what happens on an unknown or ambiguous instance.

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?

The schema documents 'instance' in detail but leaves forgetBrowserProfile undocumented (50% coverage); the description compensates by explaining precisely what setting that flag to true does. It does not clarify the default when the flag is omitted, which is the one remaining gap.

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 — deleting stored browser-session cookies of an instance — and the title 'Forget a browser session' reinforces it. It is clearly the inverse of jira_login, though it never explicitly distinguishes itself from jira_remove_instance or says whether server-side credentials are also revoked.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the teardown counterpart to jira_login. There is no explicit when-to-use or when-not-to-use statement, and no warning that logging out may break subsequent calls that rely on the cached session.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.