Skip to main content
Glama
Sign In
Shopify Theme Inspector MCP

Shopify Theme Inspector MCP

by dragnoir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

logout

Removes saved OAuth2 and legacy sessions for a Shopify store, ending authenticated access and requiring fresh login.

Instructions

Remove saved authentication (both OAuth2 and legacy sessions) for a Shopify store

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": {
      "storeUrl": "<storeUrl>"
    },
    "name": "logout"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeUrlYesThe Shopify store URL to logout from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates a destructive action ('Remove saved authentication'), which is helpful, but it does not mention any prerequisites, side effects (e.g., needing to re-authenticate), or whether the operation is irreversible.

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?

The description is a single, front-loaded sentence with no wasted words. It immediately states the action and scope, making it highly efficient and easy to parse.

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?

Given the tool's simplicity (one required parameter, no output schema), the description adequately covers the core functionality. However, it could be more complete by mentioning expected outcomes (e.g., success/failure response) or preconditions, but those are not critical given the clear purpose.

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?

The input schema fully documents the storeUrl parameter (100% coverage), so the description's mention of 'a Shopify store' adds only minimal confirmation of the parameter's purpose without providing extra format, constraints, or usage details.

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?

The description uses the specific verb 'Remove' and clearly identifies the resource: 'saved authentication' for a Shopify store. It also distinguishes from sibling login tools by explicitly mentioning both OAuth2 and legacy sessions, making the tool's unique purpose obvious.

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?

The context implies this tool is for logging out or clearing saved credentials, but it does not explicitly state when to use it versus alternatives. No alternatives are named, and there is no when-to-use or when-not-to-use guidance beyond the basic action.

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

Deploy Server

Other Tools