Skip to main content
Glama

get_clinks

Retrieve messages from Clink groups with filters for group, time range, and read status. Use to access group communications and manage unread content.

Instructions

Get clinks from Clink groups. Can filter by group, time range, and limit. Use check_inbox for a quick unread check.

    Args:
        group: Filter clinks to a specific group by slug (e.g., "backend-team") or ID. If not provided, returns clinks from all your groups.
        since: ISO timestamp. Only return clinks after this time. Example: 2024-01-15T10:00:00Z
        limit: Maximum number of clinks to return. Default 50, max 100.
        unread_only: If true, only return unread clinks. Default: false.
        mark_read: If true, mark returned clinks as read. Default: false.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNo
sinceNo
limitNo
unread_onlyNo
mark_readNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes filtering capabilities and the 'mark_read' parameter's effect, which adds useful context. However, it lacks details on permissions, rate limits, error handling, or what 'clinks' actually are, leaving gaps in behavioral understanding.

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 description is well-structured with a brief overview followed by detailed parameter explanations. It's appropriately sized, but the first sentence could be more front-loaded with key information, and the formatting uses indentation that might be unnecessary in some contexts.

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

Completeness4/5

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

Given the tool's complexity (5 parameters, no annotations, but with an output schema), the description does a good job covering input semantics and usage guidance. The output schema likely handles return values, so the description doesn't need to explain those. However, it could better clarify the tool's overall behavior and relationship to other tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant value beyond the input schema, which has 0% description coverage. It explains each parameter's purpose, provides examples (e.g., 'backend-team' for group, ISO timestamp format), states defaults, and clarifies behavior (e.g., 'If not provided, returns clinks from all your groups'). This fully compensates for the schema's lack of descriptions.

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?

The description clearly states the verb ('Get') and resource ('clinks from Clink groups'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'check_inbox' beyond mentioning it as an alternative for quick unread checks, which is helpful but not a full distinction from all siblings.

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?

The description provides clear guidance by naming an alternative tool ('check_inbox for a quick unread check') and implying usage scenarios through parameter descriptions (e.g., filtering by group, time range). However, it doesn't explicitly state when NOT to use this tool or compare it to other siblings beyond 'check_inbox'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Voxos-ai-Inc/clink-mcp-server-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server