Skip to main content
Glama

Nevent MCP

by io.github.nevent-dev

nevent_get_short_url

Read-only

Get complete details of a specific short URL including target URL, metadata, creation date, expiration, tags, and current click count. Use after nevent_list_short_urls to get the id. Key fields returned: id, shortCode, shortUrl, longUrl, title, tags, metadata, clickCount, lastClickedAt, isActive, isExpired, isParent, parentShortCode, userId, userLinksCount. Use the returned id with nevent_get_short_url_metrics for time-series analytics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMongoDB ObjectId of the short URL (24 hex characters). Obtain from nevent_list_short_urls response field "id".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by enumerating the exact fields returned (id, shortCode, clickCount, etc.) and the relationship to other tools (use returned id with metrics). It does not contradict annotations and provides behavioral context beyond the structured data.

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?

Two sentences with no filler. The first sentence states the purpose and included content; the second lists key fields and points to the metrics tool. All information is front-loaded and earns its place.

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?

For a simple read operation with one parameter, the description is complete: schema covers the parameter, annotations cover safety, and the description lists all returned fields (since there is no output schema) and explains the usage sequence. No critical information is missing for an agent to call this tool correctly.

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?

The input schema already covers the single parameter 'id' with a full description including format and source ('Obtain from nevent_list_short_urls response field "id"'). The description repeats this same guidance without adding new meaning, so the baseline of 3 applies given the 100% schema coverage.

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?

States a specific verb ('Get') and resource ('complete details of a specific short URL') and enumerates the content (target URL, metadata, dates, tags, click count). Clearly distinguishes from siblings like nevent_list_short_urls (which lists, not details) and nevent_get_short_url_metrics (which is for analytics, not details).

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?

Explicitly instructs to call after nevent_list_short_urls to obtain the id, and directs to nevent_get_short_url_metrics for time-series analytics. This provides clear sequencing and routes to the appropriate alternative tool, leaving no ambiguity about when to use this tool vs. others.

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

All Nevent MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most domain groups are distinct, but the campaign reporting cluster has three tools returning overlapping engagement metrics (get_campaign, get_campaign_metrics, campaign_report), and paid_ads_status vs paid_ads_health have fuzzy boundaries. The detailed descriptions mitigate but do not eliminate the risk of an agent calling the wrong tool.

Naming Consistency3/5

All names use the nevent_ prefix and snake_case, and most CRUD operations follow verb_noun. However, several tools reverse the order or drop the verb entirely (segment_preview, segment_execute, campaign_report, paid_ads_status, analytics_query), making the convention mixed but still readable.

Tool Count1/5

With 59 tools, this is far above the 25+ 'too many' threshold and falls into the 50+ extreme range. The broad domain coverage explains some of the size, but for an agent the set is likely to be overwhelming and harder to navigate than a more focused server.

Completeness3/5

The core marketing workflow (segments, templates, campaign creation, quote, schedule, metrics) is covered, but there is no way to update, cancel, or delete a campaign, and templates and segments lack delete operations. These are notable lifecycle gaps that agents will hit when users want to change or clean up resources.

Resources