BinaSmart MCP Server

Job vacancies in Ethiopia

list_jobs

Read-only

Search open Ethiopian job vacancies on BinaSmart by keyword in English or Amharic, field, or city, returning company, location, deadline, salary, and requirements.

Instructions

Open job vacancies in Ethiopia listed on BinaSmart (bina.et/jobs): the job title, the company posting it, the city, the deadline and days left, salary and requirements where the advert states them. Thousands of vacancies from Ethiopian job boards and employers, refreshed every morning. Search by keyword in English or Amharic, and filter by field of work (banking, accounting, engineering, it, health, education, sales, ngo, logistics, admin, hospitality, construction, agriculture, legal, security, media) or by city. Open vacancies only unless include_closed is set. Where the assistant shows MCP Apps, the result also appears as job cards with an apply link for each vacancy.

Input Schema

Name	Required	Description
`city`	No	City, e.g. Addis Ababa, Adama, Hawassa, Bahir Dar, Dire Dawa
`field`	No	Field of work: banking, accounting, engineering, it, health, education, sales, ngo, logistics, admin, hospitality, construction, agriculture, legal, security, media. Use list_job_fields to see what is open now.
`limit`	No	Max vacancies, default 20
`query`	No	Keyword in the job title, summary or company name — English or Amharic. Omit for the vacancies closing soonest.
`include_closed`	No	Include vacancies whose deadline has passed (default false)

Output Schema

Name	Required	Description
`jobs`	No	Open vacancies
`note`	No	How to use or present this result
`count`	No	Number of items returned
`source_url`	No	bina.et page this result comes from; cite it

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Oct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Number of items returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "jobs": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "city": {
+                "description": "City",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "closed": {
+                "description": "true if closed",
+                "type": [
+                  "boolean",
+                  "null"
+                ]
+              },
+              "days_left": {
+                "description": "Days until the deadline",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "deadline": {
+                "description": "Application deadline",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "employer": {
+                "description": "Employer",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "employer_url": {
+                "description": "Employer page",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "field": {
+                "description": "Field",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "slug": {
+                "description": "Job slug for get_job",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "description": "Job title",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "url": {
+                "description": "Job page",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Open vacancies"
+    },
+    "note": {
+      "description": "How to use or present this result",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Oct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description adds real context: daily morning refresh, sourcing from multiple Ethiopian job boards and employers, server-side default of open vacancies only, and a UI caveat that results render as job cards with apply links under MCP Apps.

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 resource and scope, then progressively narrows to filters and defaults. It is somewhat long and repeats the field-of-work enumeration that the schema already carries, but every sentence is informational rather than filler.

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?

An output schema exists, so return values need no explanation, yet the description still covers the practical essentials: what is indexed, refresh cadence, open-vs-closed default, search language support, and the job-card rendering. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description adds marginal value by noting Amharic keyword search and that closed vacancies are excluded unless include_closed is set, but it largely restates the field-of-work list and city filter already documented in the schema.

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 ('Open job vacancies in Ethiopia listed on BinaSmart') plus the exact fields returned (title, company, city, deadline, salary, requirements). This clearly separates it from get_job (single vacancy), get_employer, and list_job_fields.

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?

It gives usable search patterns ('Search by keyword in English or Amharic, and filter by field of work or by city') and the open/closed default, but it never routes to alternatives such as get_job for a single vacancy or list_job_fields for field discovery. Usage is implied rather than explicitly delimited.

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