Spicrawl

Get a session

spicrawl_session_get

Read-onlyIdempotent

Return one session's metadata: status, engine (its rendering tier), proxy/exit, usage count, expiry, lease holder, and a summary of its stored context. Never returns the credentials themselves (use spicrawl_session_context for that).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes	The session id returned by spicrawl_session_create or spicrawl_session_list.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Session id; pass it as `session_id` to spicrawl_scrape.
`lease`	No	Present only while a scrape holds the session; release and delete are refused until it lapses unless `force`.
`proxy`	No	The session's exit intent (never an IP or endpoint).
`engine`	No	Rendering tier the session is bound to: fetch, js or browser.
`status`	No	active, released or expired; derived from the clock, and only `active` sessions can be used.
`context`	No	Size summary of the stored context (counts only, no secrets); null once the session is not active.
`retired`	No	Why the session was taken out of service (expired, usage_exhausted, explicit); absent while usable.
`warnings`	No	Decisions made on your behalf at creation, e.g. a TTL reduced to the organization maximum.
`created_at`	No	Creation time, RFC 3339 UTC.
`expires_at`	No	Current expiry (slides on use), RFC 3339 UTC.
`project_id`	No	Project the session belongs to.
`sticky_key`	No	Exit pin in use (empty when rotate_ip was set).
`fingerprint`	No	Browser fingerprint, as stored.
`released_at`	No	Release time, on released sessions, RFC 3339 UTC.
`usage_count`	No	Successful scrapes that used the session.
`last_used_at`	No	Last successful scrape, RFC 3339 UTC; null if never used.
`domain_scores`	No	Per-domain standing, keyed by domain. Omitted when empty.
`hard_expires_at`	No	Fixed ceiling the expiry never passes, RFC 3339 UTC.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "context": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "bytes": {
+              "description": "Serialised size of the stored context.",
+              "type": "integer"
+            },
+            "cookies": {
+              "description": "Cookies stored.",
+              "type": "integer"
+            },
+            "origins": {
+              "description": "Distinct origins with stored web storage.",
+              "type": "integer"
+            },
+            "schema_version": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Size summary of the stored context (counts only, no secrets); null once the session is not active."
+    },
+    "created_at": {
+      "description": "Creation time, RFC 3339 UTC.",
+      "type": "string"
+    },
+    "domain_scores": {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "bad": {
+            "description": "Failed requests counted.",
+            "type": "integer"
+          },
+          "good": {
+            "description": "Successful requests counted.",
+            "type": "integer"
+          },
+          "last_updated": {
+            "description": "Last update, Unix milliseconds.",
+            "type": "number"
+          },
+          "retired": {
+            "description": "Hard block for this domain; use a new session for it.",
+            "type": "boolean"
+          },
+          "score": {
+            "description": "Error score; rises on failures, decays on successes. Blocked at 3.",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "description": "Per-domain standing, keyed by domain. Omitted when empty.",
+      "type": "object"
+    },
+    "engine": {
+      "description": "Rendering tier the session is bound to: fetch, js or browser.",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "Current expiry (slides on use), RFC 3339 UTC.",
+      "type": "string"
+    },
+    "fingerprint": {
+      "additionalProperties": {},
+      "description": "Browser fingerprint, as stored.",
+      "type": "object"
+    },
+    "hard_expires_at": {
+      "description": "Fixed ceiling the expiry never passes, RFC 3339 UTC.",
+      "type": "string"
+    },
+    "id": {
+      "description": "Session id; pass it as `session_id` to spicrawl_scrape.",
+      "type": "string"
+    },
+    "last_used_at": {
+      "description": "Last successful scrape, RFC 3339 UTC; null if never used.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "lease": {
+      "additionalProperties": true,
+      "description": "Present only while a scrape holds the session; release and delete are refused until it lapses unless `force`.",
+      "properties": {
+        "expires_at": {
+          "description": "When the lease lapses at the latest, RFC 3339 UTC.",
+          "type": "string"
+        },
+        "holder": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "project_id": {
+      "description": "Project the session belongs to.",
+      "type": "string"
+    },
+    "proxy": {
+      "additionalProperties": true,
+      "description": "The session's exit intent (never an IP or endpoint).",
+      "properties": {
+        "country": {
+          "description": "Lowercase alpha-2 exit country, when one was requested.",
+          "type": "string"
+        },
+        "region_pool": {
+          "description": "Regional pool requested at creation.",
+          "type": "string"
+        },
+        "tier": {
+          "description": "Exit tier: datacenter or residential.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "released_at": {
+      "description": "Release time, on released sessions, RFC 3339 UTC.",
+      "type": "string"
+    },
+    "retired": {
+      "description": "Why the session was taken out of service (expired, usage_exhausted, explicit); absent while usable.",
+      "type": "string"
+    },
+    "status": {
+      "description": "active, released or expired; derived from the clock, and only `active` sessions can be used.",
+      "type": "string"
+    },
+    "sticky_key": {
+      "description": "Exit pin in use (empty when rotate_ip was set).",
+      "type": "string"
+    },
+    "usage_count": {
+      "description": "Successful scrapes that used the session.",
+      "type": "integer"
+    },
+    "warnings": {
+      "description": "Decisions made on your behalf at creation, e.g. a TTL reduced to the organization maximum.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

First observedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds valuable non-obvious behavior: it never returns credentials and points to the sibling tool that does, plus it lists the metadata fields exposed. It does not cover error behavior or lease semantics in depth.

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 tightly written sentences with no wasted words. The returned fields are front-loaded, and the credential limitation and alternative are appended as the key exception, making the structure easy to parse.

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 single-parameter read tool with an output schema and rich annotations, the description is complete enough. It clarifies the return contents and the credential boundary, and the output schema handles the detailed response structure, leaving no critical gap for correct invocation.

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?

Schema description coverage is 100%, so the session_id parameter is already fully documented in the schema, including where it comes from. The description adds no additional syntax, format, or constraint details for the parameter, so the baseline score of 3 applies.

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 states a specific verb (Return) and resource (one session's metadata) and enumerates the exact fields returned. It also explicitly distinguishes itself from the sibling spicrawl_session_context by noting it never returns credentials, so an agent can tell the two apart without opening either schema.

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?

It gives a clear context for use (fetch a session's metadata) and an explicit alternative for the credential case ('use spicrawl_session_context for that'). However, it does not state when to prefer this over spicrawl_session_list or describe prerequisites for calling it, so it falls short of full when/when-not guidance.

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

All Spicrawl tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?