Skip to main content
Glama

Store: Reauthorize Connection

start_store_reauthorization

[Store] [What it does] Requests a platform reauthorization link for an owned store; generating the link does not mean reauthorization is complete. [When to use] Use for a store with a connection error, expired authorization, or another reconnection need. [When not to use] For a brand-new store connection, use start_store_connection; this tool is only for reauthorizing an existing store. [How to use] Copy dsers_store_id from list_stores after checking current status. A successful response returns dsers_store_id, sales_store_name, sales_channel_id, a validated HTTPS authorization_url, and generated_at; this means only that the link was generated. The upstream platform controls its lifetime and reuse policy. If the outcome is unresolved, verify with list_stores before retrying. [Side effects] Generating the link does not change authorization status. [Confirmation] Requires user confirmation before generating the link; skippable per authorization policy. [Follow-up] Give the returned authorization_url to the user to complete platform authorization, then verify the connection with list_stores.

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": {
      "dsers_store_id": "<dsers_store_id>"
    },
    "name": "start_store_reauthorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_store_idYesCopy from list_stores response dsers_store_id field. Decimal string like "123456". Required.

Output Schema

NameRequiredDescriptionDefault
generated_atYesRFC3339 time when this result was generated
dsers_store_idYesOwned DSers store ID as a decimal string
sales_channel_idNoSales channel ID as a decimal string
sales_store_nameNoSales store display name
authorization_urlNoPlatform reauthorization URL when refresh is allowed
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, destructiveHint=false, and idempotentHint=false, and the description goes further: link generation does not change authorization status, the upstream platform controls lifetime and reuse, user confirmation is required (skippable), and unresolved outcomes should be verified via list_stores. The one unaddressed point is that readOnlyHint=false while the description emphasizes no state change – a minor tension, not a contradiction, since an upstream resource is created.

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?

Bracketed section headers make it scannable and front-loaded, with no wasted prose. The enumeration of return fields is somewhat redundant given an output schema exists, which keeps it from a 5.

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 the full lifecycle an agent needs: prerequisites, side effects, confirmation policy, expected response semantics, and a follow-up verification step. Nothing material is missing for a single-parameter tool with rich annotations and an output schema.

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% and the schema already documents dsers_store_id's format and source, so a baseline 3 would apply. The description adds workflow meaning beyond that: check current status first via list_stores, then copy the id, which prevents calling it on a healthy store.

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: 'Requests a platform reauthorization link for an owned store.' It immediately distinguishes itself from start_store_connection by scoping to existing stores needing reconnection, so an agent can pick it without opening sibling schemas.

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 triggers (connection error, expired authorization, reconnection need) and an explicit when-not-to-use rule routing brand-new connections to start_store_connection. Both the positive and negative cases are named.

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.