Skip to main content
Glama
Sign In
irantalent-mcp

irantalent-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search jobs

it_search_jobs
Read-onlyIdempotent

Search IranTalent job ads by keyword, location, category, seniority, work type and other filters, with results sorted newest first.

Instructions

Search IranTalent job ads by keyword and filters, newest first.

Slugs from it_lookups; several in one filter = OR, different filters = AND. Salary is Toman per month, only if the employer shows it. Next: it_job, it_company. total is the full match count.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based; 30 per page.
urgentNoOnly fast-hiring jobs (filters this page only).
companyNoOnly this company's jobs.
keywordNoJob name or ad text words, English or Persian, e.g. python, حسابدار.
promotedNoOnly promoted ads.
locationsNoCity/province slugs from it_lookups('locations'), e.g. ['tehran'].
seniorityNoSlugs from it_lookups('seniority').
work_typeNoWork arrangement.
categoriesNoSlugs from it_lookups('categories').
employmentNoSlugs from it_lookups('employment').
industriesNoSlugs from it_lookups('industries').
military_serviceNoOnly military-service (امریه) ads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.2.0
    • changedInput schema / properties / categories / description
      Previous value: -"Job category slugs from it_lookups(kind='categories')."New value: +"Slugs from it_lookups('categories')."
    • changedInput schema / properties / company / anyOf
      Previous value: -[
-  {
-    "description": "Company id (a UUID) from it_search_jobs (company.id), it_companies or it_top_companies.",
-    "pattern": "^[0-9a-fA-F-]{36}$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Company UUID from it_search_jobs, it_companies or it_top_companies.",
+    "pattern": "^[0-9a-fA-F-]{36}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / company / description
      Previous value: -"Only this company's jobs (company id)."New value: +"Only this company's jobs."
    • changedInput schema / properties / employment / description
      Previous value: -"Employment type slugs from it_lookups(kind='employment') (full time, part time, freelance)."New value: +"Slugs from it_lookups('employment')."
    • changedInput schema / properties / industries / description
      Previous value: -"Industry slugs from it_lookups(kind='industries')."New value: +"Slugs from it_lookups('industries')."
    • changedInput schema / properties / keyword / description
      Previous value: -"Words from the job name or ad text, English or Persian, e.g. python, حسابدار."New value: +"Job name or ad text words, English or Persian, e.g. python, حسابدار."
    • changedInput schema / properties / locations / description
      Previous value: -"City or province slugs from it_lookups(kind='locations'), e.g. ['tehran', 'isfahan']."New value: +"City/province slugs from it_lookups('locations'), e.g. ['tehran']."
    • changedInput schema / properties / military_service / description
      Previous value: -"Only ads open to military-service assignment (امریه سربازی)."New value: +"Only military-service (امریه) ads."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based. 30 results per page."New value: +"1-based; 30 per page."
    • changedInput schema / properties / promoted / description
      Previous value: -"Only the employer-promoted (boosted) ads."New value: +"Only promoted ads."
    • changedInput schema / properties / seniority / description
      Previous value: -"Seniority slugs from it_lookups(kind='seniority'), e.g. ['top-management-director']."New value: +"Slugs from it_lookups('seniority')."
    • changedInput schema / properties / urgent / description
      Previous value: -"Only jobs flagged as fast hiring (applied to this page of results only)."New value: +"Only fast-hiring jobs (filters this page only)."
    • changedInput schema / properties / work_type / description
      Previous value: -"Where the work happens."New value: +"Work arrangement."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are ordered newest-first, salary values are Toman per month and only present when the employer discloses them, and `total` is the full match count rather than the page size. It does not discuss rate limits or response field shape, keeping it below 5.

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?

Four short sentences, front-loaded with purpose then the combination rule, the currency caveat, and the routing hint. Nothing is repeated from the schema and no sentence is filler.

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

Completeness4/5

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

With 12 optional parameters, no output schema and full annotation coverage, the description supplies the pieces an agent would otherwise have to guess: filter composition, sort order, salary semantics, and the meaning of `total`. What is missing is any indication of the returned job fields, which matters slightly given there is no output schema.

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 description coverage is 100%, so baseline would be 3. The description earns above baseline by explaining cross-parameter semantics the schema cannot express: OR within a single list filter, AND across different filters, and the unit/conditional-presence of salary. It does not elaborate on individual filter meanings beyond what the schema already says.

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 opens with a specific verb and resource — 'Search IranTalent job ads by keyword and filters' — plus a default ordering ('newest first'). It also names the natural follow-up tools (it_job, it_company), so an agent can place it in the toolset without opening the 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 clear operating context: slug filters must come from it_lookups, and results feed into it_job / it_company for detail. The combination rule ('several in one filter = OR, different filters = AND') is explicit guidance. It stops short of naming when NOT to use this tool (e.g. versus it_similar_jobs or it_job_market), so it is not a full 5.

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