iGods GEO Visibility Tool (GVT)

List tests

gvt_list_tests

Read-onlyIdempotent

List visibility tests for the authenticated user, newest first. Supports filtering by domain (optionally including subdomains), by URL (exact or contains match), by creation date range, by status, and by test type. This is the tid and history discovery surface: use it to find the exact recorded URL string and tids that gvt_get_baseline, gvt_get_latest, and gvt_get_test_results require, and use gvt_get_score_trend instead when you only need baseline-vs-latest deltas — it skips the paging entirely.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	URL to filter tests by; matched per urlMode (contains by default).
`limit`	No	Max results to return (default 10, max 100)
`domain`	No	Domain to filter tests by, e.g. example.com. Subdomains are included unless includeSubdomains is false.
`offset`	No	Number of records to skip before returning results (not a page number). Use offset=0 for the first page, offset=limit for the second page, etc.
`status`	No	Test status to filter by: pending, processing, completed, or failed.
`urlMode`	No	How the url filter matches: "exact" for full-URL equality, "contains" for substring match.	contains
`testType`	No	Test type to filter by: url, html, or html_paste.
`createdTo`	No	Exclusive creation-date upper bound. YYYY-MM-DD (UTC midnight) or full ISO 8601 instant.
`createdFrom`	No	Inclusive creation-date lower bound. YYYY-MM-DD (UTC midnight) or full ISO 8601 instant.
`sortDirection`	No	Sort direction by creation date: desc (newest first, default) or asc (oldest first).	desc
`includeSubdomains`	No	If true (the default), includes tests for subdomains of the given domain. Set false to match the exact domain only.

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size actually applied
`tests`	No	The matching test sessions on this page
`total`	No	Total matching tests before pagination
`ttlMs`	No	Suggested client cache lifetime in milliseconds
`domain`	No	The domain filter actually applied, if any
`offset`	No	Row offset applied to this page
`hasMore`	No	True when more pages exist
`createdTo`	No	Effective upper creation-date bound, if any
`nextOffset`	No	Offset for the next page, null on the last page
`createdFrom`	No	Effective lower creation-date bound, if any
`includeSubdomains`	No	Whether subdomains were included in the domain filter

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 10, 2026
- addedOutput schema / properties / createdFrom / description
```
Added value: +"Effective lower creation-date bound, if any"
```
- addedOutput schema / properties / createdTo / description
```
Added value: +"Effective upper creation-date bound, if any"
```
- addedOutput schema / properties / domain / description
```
Added value: +"The domain filter actually applied, if any"
```
- addedOutput schema / properties / hasMore / description
```
Added value: +"True when more pages exist"
```
- addedOutput schema / properties / includeSubdomains / description
```
Added value: +"Whether subdomains were included in the domain filter"
```
- addedOutput schema / properties / limit / description
```
Added value: +"Page size actually applied"
```
- addedOutput schema / properties / nextOffset / description
```
Added value: +"Offset for the next page, null on the last page"
```
- addedOutput schema / properties / offset / description
```
Added value: +"Row offset applied to this page"
```
- addedOutput schema / properties / tests / description
```
Added value: +"The matching test sessions on this page"
```
- addedOutput schema / properties / total / description
```
Added value: +"Total matching tests before pagination"
```
- addedOutput schema / properties / ttlMs / description
```
Added value: +"Suggested client cache lifetime in milliseconds"
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Filtered, paginated test history, newest first",
+  "properties": {
+    "createdFrom": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "createdTo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "domain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hasMore": {
+      "type": "boolean"
+    },
+    "includeSubdomains": {
+      "type": "boolean"
+    },
+    "limit": {
+      "type": "integer"
+    },
+    "nextOffset": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "tests": {
+      "items": {
+        "description": "Test session summaries (tid, url, status, analysisSummary, createdAt)",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "ttlMs": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description does not contradict them. It adds contextual value by framing the tool as a discovery surface and stating the default ordering (newest first), which supplements the safety profile without duplicating it.

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 structured with the primary purpose front-loaded, a concise list of filter capabilities, and a valuable routing note at the end. Every sentence earns its place, and the length is appropriate for an 11-parameter tool.

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?

The description fully complements the rich schema and output schema. It explains the tool's role in the workflow, tells the agent exactly how to use it to obtain tids and URL strings for sibling tools, and provides an alternative for simpler needs. Nothing an agent needs to call or route correctly is missing.

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 100% schema description coverage, the schema already documents all 11 parameters including defaults and enums. The description mentions filter options (domain, URL, date range, status, test type) but adds no new parametric detail beyond what the schema covers; it is a baseline 3.

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 lists visibility tests for the authenticated user, newest first. It further positions it as the 'tid and history discovery surface' and distinguishes it from gvt_get_score_trend, making its purpose specific and unambiguous.

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 tells when to use this tool (to find tids and URL strings needed by related tools) and when not to (use gvt_get_score_trend for deltas). It names the alternative and the condition that selects it, leaving no ambiguity.

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

All iGods GEO Visibility Tool (GVT) 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?