Skip to main content
Glama

List EDD Customers

edd_list_customers

Retrieve customers with purchase statistics, including creation date and additional emails. Filter by date preset (today/yesterday) or custom range.

Instructions

List customers with their purchase statistics (date_created, additional_emails included). Optionally filter by creation date preset (today/yesterday) or a custom date range in YYYYMMDD format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberNoNumber of customers to return (default: 10)
pageNoPage number for pagination
dateNoFilter by creation date preset
startDateNoStart date in YYYYMMDD format (requires endDate)
endDateNoEnd date in YYYYMMDD format (requires startDate)
Behavior3/5

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

No annotations provided. Description reveals return includes purchase statistics but lacks details on pagination, ordering, or response format. Acceptable for a simple list tool but not comprehensive.

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 sentences, direct, no redundancy.

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?

Adequate for a list tool with full schema coverage, but lacks documentation of response structure or pagination behavior. Could specify what 'purchase statistics' includes.

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 covers all parameters. Description adds functional context: date enum values and custom range requirement. Also mentions additional fields not in schema.

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?

Clearly states 'List customers' and specifies included fields (purchase statistics, date_created, additional_emails). Distinguishes from singular 'edd_get_customer' sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this vs other list tools (e.g., edd_list_sales). Only implies usage for customer listing with optional date filters.

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/verygoodplugins/mcp-edd'

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