Skip to main content
Glama
Sign In
PageSift

PageSift

by YOLOW92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Close a kept page

pagesift_interact_stop
Destructive

Close a kept browser page and free its memory once you finish with the session; the scrapeId becomes invalid, so later calls with it fail.

Instructions

Close a browser page kept by pagesift_scrape keepSession or pagesift_interact and free its memory. Data already returned stays with the caller; the scrapeId becomes invalid, so later calls with it fail. Calling stop twice or after expiry returns an error. Pages expire automatically after 10 minutes if never stopped, and are reclaimed sooner when idle under memory pressure.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scrapeId": "<scrapeId>"
    },
    "name": "pagesift_interact_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
scrapeIdYesmetadata.scrapeId of the kept page.

Output Schema

NameRequiredDescriptionDefault
successYesThe page was closed.
sessionDurationMsYesHow long the page stayed open, in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "sessionDurationMs": {
+      "description": "How long the page stayed open, in milliseconds.",
+      "type": "integer"
+    },
+    "success": {
+      "description": "The page was closed.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "sessionDurationMs"
+  ],
+  "type": "object"
+}
  2. Addedv0.81.6

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the supplied annotations (destructiveHint=true, idempotentHint=false) by spelling out what destruction means: already-returned data stays with the caller, the scrapeId becomes invalid so subsequent calls fail, double-calls error, and pages auto-expire after 10 minutes or are reclaimed earlier under memory pressure. This directly explains why the operation is neither idempotent nor safely repeatable.

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?

Three tight sentences, front-loaded with the action and effect, then consequences, then failure/expiry conditions. No filler and every clause carries operational information.

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 one-parameter lifecycle tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what is freed, what remains valid, what fails, and what happens if it is never called. Return-value documentation is correctly omitted since an output schema exists.

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 coverage is 100% and the single parameter is already documented as 'metadata.scrapeId of the kept page', so the baseline is 3. The description adds only the lifecycle fact that this id becomes invalid after the call, which is about consequences rather than the parameter's format or source.

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?

States a specific verb and resource ('Close a browser page') plus the side effect ('free its memory'), and names the exact sibling tools that create such a page (pagesift_scrape keepSession, pagesift_interact). An agent can distinguish it from the other seven siblings without reading schemas.

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?

Implicitly scopes usage to pages kept via keepSession or interact, and explicitly warns that a second call or a call after expiry errors, which steers the agent away from blind retries. It stops short of an explicit 'use X instead when you still need the page data' routing statement, so it is clear context rather than a full when/when-not matrix.

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

Deploy Server

Other Tools