ScreenConnect MCP Server

screenconnect_sessions_search

Read-onlyIdempotent

Search ScreenConnect sessions by name, machine, user, type, OS, online status, or custom properties, or apply an advanced raw filter to narrow results.

Instructions

Search sessions using safely quoted structured fields or an exclusive advanced raw filter. Pagination is client-side.

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": "screenconnect_sessions_search"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`limit`	No
`filter`	No
`offset`	No
`includeRaw`	No
`onlineOnly`	No
`machineName`	No
`sessionType`	No
`loggedOnUser`	No
`serialNumber`	No
`operatingSystem`	No
`customProperties`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is lower, and the description still adds two non-obvious behaviors: pagination happens client-side (affecting how limit/offset behave) and the raw filter is exclusive of structured fields. It omits result shape and any note on how large a client-side page can practically be, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core search behavior and no filler. Efficient, though the terseness borders on under-specification for a 12-parameter tool rather than being merely economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter search with a nested object, zero schema descriptions, and no output schema, the definition leaves most of the surface unexplained — notably customProperties, onlineOnly, includeRaw, and what a returned session record contains. The client-side pagination warning is valuable but not enough to make it callable with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, including a nested customProperties object with eight undocumented slots, so the description must carry the burden. It only conveys the structured-fields vs. raw-filter dichotomy (and hints pagination applies to offset/limit); includeRaw, onlineOnly, sessionType enum, and the custom property keys get no meaning at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a clear verb and resource ("Search sessions") and identifies the two search modes: structured fields vs. an advanced raw filter. That is more specific than a generic "search sessions" and lets an agent distinguish it from get_by_name / get_details siblings, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Exclusive advanced raw filter" is a real usage rule: the raw filter cannot be combined with the structured field parameters, which guides an agent's choice. However, there is no guidance on when to use this tool versus list_online or get_by_name, and no prerequisites or exclusions are stated.

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

Deploy Server