Skip to main content
Glama
Sign In

Piku

by com.usepiku
OverviewDiscussionsAdmin

Read your page insights

get_insights
Read-onlyIdempotent

Creators only, on their own Piku account (asks them to connect). Page insights for the connected creator's public page over the last 30 days: visits, taps, tap rate (visits with a tap) and Rate requests, each with the change against the 30 days before; each link and widget in page order with the share of visits that saw it and its tap rate; sources; countries; the busiest two hours for taps in the creator's time zone; the Rate path; and the one open suggestion. Counts only, never who. Read only. When Page insights is not open on the account, says so.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, yet the description still adds substantive behavior: a fixed 30-day window with comparison to the prior 30 days, an OAuth-style connect prompt, an aggregation guarantee ('Counts only, never who'), and the disclosure that a disabled insights panel produces an explanatory message rather than data.

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 audience and precondition are front-loaded, and the long semicolon-delimited inventory of returned metrics is readable as a list of what comes back. It is a single sprawling sentence, though, and a couple of clauses (e.g. 'the Rate path', 'the one open suggestion') would read faster as a bulleted enumeration.

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

Completeness5/5

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

With no output schema and zero parameters, the description carries full responsibility for describing the return payload, and it discharges that by naming every section and metric plus the time window used for deltas. The auth requirement and disabled-panel behavior close the remaining gaps an agent would otherwise hit at call time.

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 no parameters, so there is nothing for the description to disambiguate; the 4 baseline applies. The description correctly avoids inventing parameter-like options such as a date range that the schema does not support.

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?

States a specific verb and resource ('Page insights for the connected creator's public page') and then enumerates the exact metrics returned, so an agent knows precisely what it gets. It does not explicitly contrast itself with the sibling 'get_page', which is the one nearby ambiguity an agent might have.

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?

'Creators only, on their own Piku account (asks them to connect)' establishes the actor and precondition for use, and the closing clause covers the not-enabled case. There is no explicit statement of when to prefer this over get_page or other analytics-adjacent siblings, so it stops short of full when/when-not guidance.

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

All Piku toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources