Skip to main content
Glama
Sign In
merch-connector

merch-connector

by grahamton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

clear_session

Clear stored session for a domain by wiping cookies and cached page data to start fresh, test logged-out vs logged-in experiences, or force a fresh scrape.

Instructions

Clear the stored session for a domain — wipes both cookies and cached page data. Use this to start fresh (e.g., test logged-out vs logged-in experience, or force a fresh scrape).

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": {
      "url": "<url>"
    },
    "name": "clear_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAny URL on the domain to clear (e.g., "https://www.zappos.com").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the destructive behavior of wiping cookies and cached data, and notes the domain scope. It doesn't mention irreversibility or session storage details beyond cookies/cache, but for a simple tool this is adequate.

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 two sentences: first states the purpose and mechanics, second gives usage examples. Every word earns its place with no redundancy or filler.

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 one-parameter, no-output-schema tool, the description is complete. It covers what the tool does, what it affects, and when to use it. No additional context is needed.

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?

Schema coverage is 100% with a clear parameter description. The tool description adds value by clarifying that any URL on the domain works, not just the exact homepage, and provides an example. This goes beyond the schema's basic description.

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 clearly states the tool's function with a specific verb and resource: 'Clear the stored session for a domain' and specifies exactly what is wiped (cookies and cached page data). This distinguishes it from sibling tools like scrape_pdp or interact_with_page.

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?

The description explicitly says 'Use this to start fresh' and provides concrete example use cases (testing logged-out vs logged-in, forcing a fresh scrape). It lacks explicit when-not-to-use guidance or alternative tool references, but the context is clear.

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