Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

hires_list_candidate_activities

Read-only

List a candidate's timeline events. Prefer size <= 10. event_type values: comment, copilot_response, stage_moved, automation_action_triggered, assign_job, enrichment, call, validate_emails, profile_mutation, qualification, assign_tags, assign_sources, candidate_rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCandidate id or alias
pageNo
sizeNoDefault 20, max 100
viewNosummary replaces copilot text, call transcription and comment body with 200-char *_preview fieldssummary
sinceNoInclusive; Unix seconds or ISO-8601
untilNoInclusive; Unix seconds or ISO-8601
event_typeNoComma-separated; values listed in the tool description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / event_type / description
      Previous value: -"Comma-separated event types to filter. Supported: comment, copilot_response, stage_moved, automation_action_triggered, assign_job, enrichment, call, validate_emails, profile_mutation, qualification, assign_tags, assign_sources, candidate_rate."New value: +"Comma-separated; values listed in the tool description"
    • changedInput schema / properties / id / description
      Previous value: -"Candidate ID (integer) or alias (string)."New value: +"Candidate id or alias"
    • removedInput schema / properties / page / description
      Removed value: -"Page number (1-based)."
    • changedInput schema / properties / since / description
      Previous value: -"Inclusive lower bound on event timestamp. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-04-01T00:00:00Z). Fractional seconds accepted but truncated."New value: +"Inclusive; Unix seconds or ISO-8601"
    • changedInput schema / properties / size / description
      Previous value: -"Page size. Values above 100 are rejected with 400. Default 20, max 100."New value: +"Default 20, max 100"
    • changedInput schema / properties / until / description
      Previous value: -"Inclusive upper bound on event timestamp. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-04-01T00:00:00Z). Fractional seconds accepted but truncated."New value: +"Inclusive; Unix seconds or ISO-8601"
    • changedInput schema / properties / view / description
      Previous value: -"Response shape. Default `summary` replaces the largest event payloads (copilot LLM response/prompt, call transcription, comment body) with 200-char `*_preview` fields. Other event types pass through unchanged. Use `full` when the original content is needed."New value: +"summary replaces copilot text, call transcription and comment body with 200-char *_preview fields"
  2. Changed5 schema fields changed
    • changedInput schema / properties / since / description
      Previous value: -"Unix timestamp (seconds) — inclusive lower bound on event timestamp."New value: +"Inclusive lower bound on event timestamp. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-04-01T00:00:00Z). Fractional seconds accepted but truncated."
    • changedInput schema / properties / since / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / size / description
      Previous value: -"Page size. Values above the max are capped. Default 20, max 100."New value: +"Page size. Values above 100 are rejected with 400. Default 20, max 100."
    • changedInput schema / properties / until / description
      Previous value: -"Unix timestamp (seconds) — inclusive upper bound on event timestamp."New value: +"Inclusive upper bound on event timestamp. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-04-01T00:00:00Z). Fractional seconds accepted but truncated."
    • changedInput schema / properties / until / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "default": "summary",
+  "description": "Response shape. Default `summary` replaces the largest event payloads (copilot LLM response/prompt, call transcription, comment body) with 200-char `*_preview` fields. Other event types pass through unchanged. Use `full` when the original content is needed.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  4. Changed3 schema fields changed
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Unix timestamp (seconds) — inclusive lower bound on event timestamp.",
+  "type": "number"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Page size. Values above the max are capped. Default 20, max 100.",
+  "type": "number"
+}
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Unix timestamp (seconds) — inclusive upper bound on event timestamp.",
+  "type": "number"
+}
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations correctly declare readOnlyHint=true and destructiveHint=false, so the description need not repeat that. The description adds value by explaining the effect of the 'view' parameter (summary replaces certain fields with previews) and the inclusive semantics of since/until, which are not in the schema. It could also mention pagination behavior, but that is minor.

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 two sentences, with the key purpose stated firstable and the crucial event_type guidance secondable. Every sentence adds distinct value: the first defines the tool's action and resource, the second gives performance and filtering advice. No filler or redundancy.

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?

Given the tool's moderate complexity (7 params), high schema coverage, and clear annotations, the description covers the essential knowledge: what it returns, how to filter, performance tips, and the meaning of the summary view. There is no output schema to worry about, and the description fills the gaps that the schema doesn't, so it is complete enough for correct invocation.

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?

Despite high schema coverage (86%), the description enriches parameter semantics by clarifying event_type values that are listed in the description but not documented in the schema. It also hints at size guidance. For the 'view' parameter, it adds context on what summary does. This goes beyond schema descriptions.

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?

The description states the tool lists a candidate's timeline events, which is specific and clear. However, it does not explicitly differentiate it from related tools like list_application_stage_history or list_candidate_messages, relying mainly on the name and the prefixed 'a candidate's timeline events' to convey scope.

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?

The description provides concrete usage guidance: it recommends using size <= 10 for better performance and enumerates valid event_type values, which helps the agent filter appropriately. It does not, however, explicitly state when this tool should be used over alternatives, but the clear event-type guidance makes the intended use case evident.

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

All 100Hires - AI ATS & Recruitment Software toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources