Skip to main content
Glama
Sign In
plausible-mcp-server

plausible-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_entry_pages

Retrieve the top entry pages where visitors first land on your site for any specified date range.

Instructions

Get top entry pages — where visitors land on your site.

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": {
      "site_id": "<site_id>",
      "date_range": "<date_range>"
    },
    "name": "get_entry_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 100)
site_idYesThe site ID (domain)
date_rangeYesDate range: '7d', '30d', 'month', 'year'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It lacks details on what 'top' means, pagination, authentication needs, or return format. The agent cannot infer behavioral traits beyond basic retrieval.

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?

Single sentence, front-loaded, no unnecessary words. Earns its place efficiently.

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 output schema and no annotations, the description is too brief. It does not explain how results are sorted, the meaning of 'entry pages', or limitations. Agent may have incomplete understanding.

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% with each parameter described. The description adds no further parameter semantics beyond what the schema provides, meeting the baseline.

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?

Clear verb+resource: 'Get top entry pages' is specific and distinguishes from sibling 'get_exit_pages'. The phrase 'where visitors land on your site' adds context.

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 implied from name and description, but no explicit when-to-use or when-not-to-use guidance is provided. No mention of alternatives like 'get_breakdown' for more detailed analysis.

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

Deploy Server

Other Tools