Skip to main content
Glama
Pixifi MCP Server

Pixifi MCP Server

pixifi_open

Opens a Pixifi admin page in your signed-in Cloud Browser, giving you access to studio clients, leads, proposals, contracts, events, and invoices for daily workflow tasks.

Instructions

Open a Pixifi page in your signed-in Cloud Browser (default https://www.pixifi.com/admin/) to work with photography studio clients, leads, proposals, contracts, events and invoices.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.pixifi.com/admin/

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?

With no annotations, the description does carry useful context by noting the browser is already 'signed-in', which tells the agent no auth step is required. It does not say whether an already-open page is reused or a new tab is created, what happens on an invalid URL, or what the tool returns, so the mutation/navigation behavior remains partly opaque.

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?

One front-loaded sentence with the action and default URL stated first. The closing enumeration of studio entities (clients, leads, proposals, contracts, events, invoices) is mildly redundant padding that does not help an agent decide or invoke.

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 one-optional-parameter navigation tool with no output schema, the definition covers the action, the session context and the default target. Only the post-call state (what page the agent ends up on, or what is returned) is unaddressed, which is a minor gap at this complexity.

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?

Schema coverage is 100% and the single parameter is optional, so the schema already documents the default URL. The description merely restates that same default, adding no format, path, or validation guidance beyond the structured field — baseline 3 is appropriate.

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 ('Open a Pixifi page') plus the medium (signed-in Cloud Browser) and a default URL. This is clearly distinguishable from pixifi_click, pixifi_read and pixifi_type, though the differentiation comes from the verb alone rather than an explicit contrast with siblings; the trailing list of studio domain objects describes the app, not the tool's action.

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 navigation/entry step before reading, clicking or typing. There is no statement of when to prefer this over pixifi_status or pixifi_guide, and no prerequisites or exclusion conditions are given.

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