Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official
by brilliantdirectories
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

createClick

Record a click event from an external source by specifying the user ID, click type, name, origin URL, and target URL.

Instructions

Create a click record - Create a new click record. Writes live data.

Use when: replicating a click event from an external source (e.g., tracking clicks on a mirrored profile page on another domain). Usually not needed - BD auto-records clicks on its own surfaces.

Required: user_id, click_type, click_name, click_from, click_url.

Parameter interactions:

  • user_id - the member profile being tracked

  • click_type - link (external), phone (reveal), or email (reveal)

  • click_from - source surface: profile_page or search_results

  • click_url - the URL that was clicked

See also: updateClick (modify existing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
click_typeYesFree-form label for the click target. NOT an enum — BD doesn't normalize and site owners create custom labels via click-tracking widgets. Common BD-canonical values (mixed casing intentional, BD does NOT normalize): `View Post`, `Profile`, `Phone Number`, `website`, `Facebook`, `Contact Form`, `Search Results`, `booking_link`, `Instagram`, `Post Link`, `LinkedIn`, `YouTube`, `Blog`, `Twitter`, `Google`, `Pinterest`. Reuse the exact casing of the value you're tracking against — `Profile` and `profile` produce two distinct rows in analytics.
click_nameYes
click_fromYesFull URL of the page where the click originated (HTTP referer). Free-form URL string; empty allowed when no referer header is present (e.g. direct hits, bot traffic). NOT an enum.
click_urlYes

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

The description adds behavioral context (writes live data, external replication use case) beyond annotations. However, it contradicts the schema by suggesting click_type has limited values (link/phone/email) while schema says free-form, reducing accuracy.

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 well-structured with sections, front-loaded purpose, and no wasted sentences. It efficiently conveys usage, requirements, and parameter details.

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 5 required params and no output schema, the description covers the use case, parameter interactions, and alternates. Missing details on response or side effects, but adequate for a creation tool.

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?

With only 40% schema description coverage, the description attempts to add meaning for all 5 parameters, but for click_type and click_from it provides restrictive interpretations that conflict with the schema's free-form nature. It adds some value but with inaccuracies.

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 clearly states the tool creates a click record and writes live data. It distinguishes from the sibling 'updateClick' by mentioning it in the 'See also' section, providing differentiation.

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?

The description explicitly states when to use (replicating external click events) and when not to (BD auto-records). It also lists required parameters and references an alternative tool (updateClick).

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/brilliantdirectories/brilliant-directories-mcp'

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