Skip to main content
Glama

shopify_list_publications

Read-onlyIdempotent

List a Shopify shop's available publications, such as Online Store and POS, to get the IDs and names needed for publishing products.

Instructions

List the shop's publications (sales channels such as Online Store, POS). Returns [{id, name}]; pass the IDs to shopify.publish_product.

Args:
    project_id: Authenticated Project UUID.
    project_ref: Exact project correlation reference.
    connector_account_ref: Project-bound connector account alias.
    idempotency_key: Stable business-action identity.
    effect: Required and must be read; Spring verifies it.
    approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectYes
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description only needs to add context beyond that; it explains that effect must be 'read' and is verified by Spring. The approval_ref line is generic write-resume boilerplate that is slightly confusing for a read-only tool, but it does not contradict the annotations.

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?

The purpose and return shape are front-loaded, and the argument list is compact with each parameter getting a single line. The 'Spring verifies it' and approval_ref phrasing is slightly generic, but the overall structure is efficient and not bloated.

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 simple read-only listing with annotations and an output schema available, the description covers what a publication is, what is returned, and how to use the result with shopify.publish_product. It could better clarify the role of optional platform parameters in this read context, but nothing critical is missing.

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 description coverage is 0%, so the description carries the full burden for parameters. It provides one-line semantics for all six parameters, including that project_id is an authenticated UUID, connector_account_ref is a project-bound alias, and effect must be read. Some definitions are abstract, but they add real meaning beyond the bare schema property names.

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 opening sentence names a specific verb and resource ('List the shop's publications') and gives concrete examples (Online Store, POS), which clearly distinguishes it from other Shopify list tools. The return-shape note and the pointer to shopify.publish_product further clarify the tool's role.

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 gives clear downstream context: the returned IDs should be passed to shopify.publish_product, which tells an agent when to use this tool. It does not explicitly call out alternatives or exclusions, but no alternative publication-list tool is apparent among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RPasquale/lightbulb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server