Skip to main content
Glama
shopify-partners-mcp

shopify-partners-mcp

by amitray007

list_apps

Read-only

Returns the Shopify Partner apps specified in SHOPIFY_PARTNER_APP_IDS, providing an app list when the Partner API has no query to enumerate all apps.

Instructions

List the apps named in SHOPIFY_PARTNER_APP_IDS. The Partner API has no query that lists every app.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are bounded by a configuration variable, so the list is not exhaustive and absence of an app is a config issue, not an error. That is the key caveat an agent needs, though return shape and behavior when the variable is empty are unstated.

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?

Two short sentences, no filler. The scoping constraint leads and the justification for the tool's existence follows, so an agent gets the essential caveat immediately.

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 zero-parameter read tool with annotations covering safety and no output schema required, the description covers source and limitation adequately. The only gap is what each returned app entry contains, which matters mildly for chaining into get_app or app_overview.

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?

The tool takes zero parameters, which is the baseline-4 case. The description correctly adds no parameter detail and instead explains where the input comes from (the env var), which is the only relevant semantic here.

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?

"List the apps" is a specific verb plus resource, and the second sentence sharpens the scope by stating the result set is limited to IDs in SHOPIFY_PARTNER_APP_IDS. It also implicitly distinguishes itself from a full enumeration by noting the Partner API offers no list-every-app query. It stops short of naming a sibling (e.g. get_app or app_overview) to route between, so it isn't a 5.

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 note that no API query lists every app implies this tool is the entry point for app discovery, which is usable context. However, it never says when to prefer list_apps over get_app or app_overview, nor what to do if an expected app is missing from the env var. Usage is implied rather than stated.

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