Skip to main content
Glama

Linq.es MCP Server

Get Profile Analytics

get_profile_analytics
Read-onlyIdempotent

Returns aggregated page views, link clicks, click-through rate (ctrPercent), top referrers, visitor countries, device categories, and daily time-series buckets for a Linq.es profile. When to use: choose this for traffic, referrer, geo, device, and CTR reporting on a Link-in-Bio page; use list_profile_links for per-link configuration and all-time link click totals, list_shortlinks for /s/:code shortlink clicks, or list_leads for contact form submissions. Prerequisites: requires Bearer lnq_live_ Pro authentication and a 'profile' handle owned by the caller (call list_profiles first if unknown). Validation: 'profile' must be non-empty and owned by the authenticated user (otherwise returns isError: true); 'days' defaults to 7, values <= 0 reset to 7, and values > 90 clamp to 90. Side effects: read-only and idempotent; performs no state mutations. Returns: JSON text with {profile, days, totalViews, totalClicks, ctrPercent, referrers, countries, devices, dailySeries: [{date, views, clicks, referrers, countries, devices, links}]}.

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": {
      "profile": "<profile>"
    },
    "name": "get_profile_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in UTC calendar days between 1 and 90 (defaults to 7 when omitted or <= 0; values above 90 are clamped to 90).
profileYesOwned Linq.es profile handle without leading '@' or URL prefix (e.g. 'alex'). Obtain valid handles from list_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / days / default
      Added value: +7
    • changedInput schema / properties / days / description
      Previous value: -"Number of days to look back (default: 7, max: 90)"New value: +"Lookback window in UTC calendar days between 1 and 90 (defaults to 7 when omitted or <= 0; values above 90 are clamped to 90)."
    • addedInput schema / properties / days / maximum
      Added value: +90
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / profile / description
      Previous value: -"Profile handle (e.g. 'alex')"New value: +"Owned Linq.es profile handle without leading '@' or URL prefix (e.g. 'alex'). Obtain valid handles from list_profiles."
    • addedInput schema / properties / profile / minLength
      Added value: +1
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Although annotations already declare read-only, idempotent, non-destructive behavior, the description adds important context: Bearer Pro authentication, ownership requirements, validation failure behavior, and the specific side-effect profile. It also describes the returned JSON structure in detail.

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 dense but front-loaded: it opens with what the tool returns, then covers usage, prerequisites, validation, side effects, and return shape. Each labeled section earns its place and no sentence is wasted.

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?

This is a non-trivial analytics tool with no output schema, and the description supplies the missing return shape, authentication prerequisite, validation behavior, and read-only guarantees. An agent has enough information to decide when and how to call it correctly.

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 coverage is 100%, so the schema already documents both parameters well. The description still adds meaningful semantics around ownership validation and error behavior for an invalid profile, and clarifies that non-positive days reset to 7 while values over 90 clamp to 90.

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?

The description states a specific verb and resource: it returns aggregated analytics metrics for a Linq.es profile. It also names the exact metrics and distinguishes itself from siblings such as list_profile_links, list_shortlinks, and list_leads.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance for traffic, referrer, geo, device, and CTR reporting, and routes the agent to the correct alternatives for per-link configuration, shortlink clicks, and leads. It also names list_profiles as the prerequisite lookup when the profile handle is unknown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.