successfactors-mcp

Overview Schema Source Related Servers Discussions Admin

ce_query

Query the SAP SuccessFactors Compound Employee SOAP API and save each XML payload page to disk for HR data extraction or troubleshooting.

Instructions

Query the EC Compound Employee (SOAP) API and save the payload to disk.

person_id_external / user_id are comma-separated and take precedence over every other filter when set. last_modified_on is an ISO datetime for a delta pull (SAP allows at most 3 months of look-back). With no filter at all this is a full extract, capped by max_pages.

CompoundEmployee SFQL allows only ONE condition on last_modified_on in the WHERE clause — a query with both a lower and an upper bound (last_modified_on>X and last_modified_on<=Y) fails with INVALID_SFQL: Only one condition is allowed. This tool only ever emits the lower bound; apply any upper bound to the returned rows client-side, not by adding a second last_modified_on condition.

last_modified_on's filtering also depends on an SFQL parameter, isNotFirstQuery, that this tool does not currently set: per tenant testing, a query without isNotFirstQuery ignores last_modified_on entirely and returns a full snapshot of the matching window, while isNotFirstQuery=true makes last_modified_on act as a real delta filter. Until this tool exposes that parameter, treat last_modified_on here as a full-window snapshot, not a guaranteed delta — don't rely on it alone to mean "only changed rows".

select_segments defaults to the widely supported COMMON_SEGMENTS. If SF answers INVALID_SFQL naming a segment, that module is not enabled on the tenant — pass a narrower list. Only documented segment names are accepted, and person_id_external / user_id values may contain only letters, digits, space and _ . @ : / + -.

Each queryMore page is written as its own XML file. The tool returns counts and paths only: one employee's payload is ~80 KB of HR data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	No
`max_rows`	No
`max_pages`	No
`company_id`	No
`select_segments`	No
`last_modified_on`	No
`person_id_external`	No
`include_contingent_workers`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations the description carries the full burden and does so thoroughly: it discloses the SFQL single-condition restriction, the isNotFirstQuery caveat that last_modified_on does NOT act as a true delta, the per-page XML file writing, and that only counts/paths are returned. These are exactly the non-obvious traits an agent needs.

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?

Front-loaded with the verb/resource, then organized into behavior, caveats, and parameter guidance. It is long, but the length is justified by the genuine SFQL and delta-pull pitfalls; a little tightening of the isNotFirstQuery passage would help.

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 high-complexity extraction tool with an output schema present, the description covers purpose, filtering semantics, SFQL limitations, and output shape (counts and paths, ~80KB per employee) without needing to restate schema fields. Nothing essential to correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate and largely does: it explains person_id_external/user_id precedence and allowed characters, last_modified_on semantics, select_segments defaulting to COMMON_SEGMENTS, and max_pages capping. However, max_rows, company_id, and include_contingent_workers receive no explanation anywhere.

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 (query the EC Compound Employee SOAP API) plus the side effect (save payload to disk). The SOAP/CompoundEmployee naming implicitly separates it from the OData-based sibling odata_query.

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?

Gives clear operating context: filter precedence for person_id_external/user_id, no-filter means full extract capped by max_pages, and the 3-month look-back limit. It stops short of explicitly naming when to prefer a sibling tool (e.g., odata_query), so it is strong context but not full alternative routing.

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

Deploy Server