Skip to main content
Glama

Measure.events Analytics

by io.github.meetclawdius
OverviewDiscussionsAdmin

Log check-in

log_checkin

Record something you did to the site (published a post, deployed, changed a page) so it shows beside the traffic it caused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
agentNoAgent name (default: the API key's name).
actionYesWhat you did, e.g. 'published /blog/launch'.
site_keyYesThe site's tracking ID (site_key), from list_sites.
timestampNoISO 8601; default now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"What the agent did (e.g. 'published article')"New value: +"What you did, e.g. 'published /blog/launch'."
    • changedInput schema / properties / agent / description
      Previous value: -"Agent name"New value: +"Agent name (default: the API key's name)."
    • removedInput schema / properties / note / description
      Removed value: -"Additional context"
    • changedInput schema / properties / site_key / description
      Previous value: -"The site's tracking ID"New value: +"The site's tracking ID (site_key), from list_sites."
    • changedInput schema / properties / timestamp / description
      Previous value: -"ISO8601 timestamp (defaults to now)"New value: +"ISO 8601; default now."
  2. First observed

TDQS

Score is being calculated.

All Measure.events Analytics 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