Kódvéna

Exit popup link

exit_popup_link

Read-onlyIdempotent

Előtöltött link az exit popup konfigurátorhoz: kilépési szándékra (mobilon gyors felgörgetésre, időre vagy görgetésre) nyíló, akadálymentes felugró ablak; ott élő előnézet és a beilleszthető, süti és külső kérés nélküli szkript.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exit_popup_link"
  }
}

Input Schema

Name	Required	Description
`link`	No	Gomb linkje (https://…, /útvonal, mailto:, tel:)
`text`	No	Szöveg
`title`	No	Cím
`button`	No	Gomb felirata
`decline`	No	Elutasító gomb felirata
`background`	No	Háttér
`every_days`	No
`coupon_code`	No	Kuponkód: ha meg van adva, a gomb ezt mutatja másolható formában (link helyett)
`button_color`	No	Gomb színe
`delay_seconds`	No
`mobile_after_seconds`	No
`mobile_after_scroll_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / coupon_code

Added value: +{
+  "description": "Kuponkód: ha meg van adva, a gomb ezt mutatja másolható formában (link helyett)",
+  "maxLength": 30,
+  "type": "string"
+}

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the read-only, idempotent, non-destructive, and closed-world annotations, it discloses the configurator workflow, live preview, embeddable output, accessibility, and the script's lack of cookies and external requests. Trigger precedence and frequency-capping behavior remain unexplained, limiting transparency for advanced configurations.

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 single sentence is front-loaded with the output, then compactly covers triggers, accessibility, preview, embedding, and privacy constraints. It is dense but contains no filler or repetition.

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?

For a 12-parameter, all-optional tool with no output schema, the description supplies the essential selection and output context: a configurator link, live preview, and an embeddable script. It supports a basic invocation well, but undocumented frequency behavior and unspecified defaults or trigger interactions prevent full completeness for advanced use.

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 67% schema coverage, much of the basic field meaning is already available in structured descriptions. The trigger sentence adds some context for delay_seconds and the mobile timing/scroll parameters, but it does not explain defaults or interactions and leaves the undocumented every_days parameter unclear.

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?

It identifies the exact output—a prefilled link to an exit-popup configurator—rather than merely restating the tool name, and explains that the configurator provides a live preview and embeddable script. This output-and-resource specificity distinguishes it from sibling generators and from tools that directly create website assets.

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 exit-intent and mobile-trigger wording establishes a clear use case: configuring an accessible popup and obtaining its preview and embeddable script through a prefilled configurator. It does not explicitly state when not to use it or route users to an alternative for other popup or banner needs.

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

All Kódvéna tools Inspect

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

Need Help?