eBird MCP Server

get_recent_checklists

Retrieve recently submitted bird observation checklists for a specified region using eBird data, helping users track recent birding activity and sightings.

Instructions

Get the most recently submitted checklists for a region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region_code": "<region_code>"
    },
    "name": "get_recent_checklists"
  }
}

Input Schema

Name	Required	Description	Default
`region_code`	Yes	Country, subnational1, subnational2, or location code
`max_results`	No	Number of checklists to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'most recently submitted' but doesn't clarify criteria like time range, sorting order, or pagination. For a retrieval tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool that retrieves data. It doesn't explain what 'most recently submitted' entails, the format of returned checklists, or any limitations, leaving the agent with insufficient context for effective use.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no additional meaning beyond implying 'region_code' is used for filtering and 'max_results' limits output, which aligns with but doesn't enhance the schema's details.

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?

The description clearly states the action ('Get') and resource ('most recently submitted checklists for a region'), making the purpose understandable. However, it doesn't explicitly differentiate from siblings like 'get_checklists_on_date' or 'get_recent_observations', which might retrieve similar temporal data but for different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_checklists_on_date' and 'get_recent_observations', there's no indication of whether this tool is preferred for checklist-specific recent data or if it overlaps with other tools, leaving usage context unclear.

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