Skip to main content
Glama
Sign In
Payhip MCP Server

Payhip MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

payhip_open

Open a Payhip page in your signed-in Cloud Browser to work with orders, products, and sales reports. Use it to navigate directly to the store admin area for seller tasks.

Instructions

Open a Payhip page in your signed-in Cloud Browser (default https://payhip.com) to work with orders, products and sales reports.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://payhip.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the meaningful context that the session is signed in and that the URL defaults to https://payhip.com. However, it says nothing about what happens if no browser session exists, whether opening is stateful/destructive, or whether the page content is returned versus merely navigated to.

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?

A single front-loaded sentence with the verb, the resource, the session type and the default all in place; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter navigation tool this covers what and where, but with no output schema the description should say whether the opened page's content is returned or whether a follow-up payhip_read is required. That gap matters for an agent deciding its next call.

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?

Only one optional parameter with 100% schema description coverage, so the schema already documents the url field and its default. The description restates the same default without adding format or validation meaning, which is the baseline rather than added value.

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 (open) and resource (a Payhip page in your signed-in Cloud Browser) with a default URL, which is enough to separate it from siblings like payhip_read or payhip_click. It stops short of explicitly contrasting itself with those siblings.

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 phrase 'to work with orders, products and sales reports' implies this is the entry point before reading, clicking or typing, but there is no explicit when-to-use or when-not-to-use guidance and no alternative named. Usage is inferable rather than stated.

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