Skip to main content
Glama

Search Yok Tez Detailed

search_yok_tez_detailed

Search the YÖK National Thesis Center by keywords across specific fields like title, author, or advisor, with filters for language, year, and access permission.

Instructions

Search the YÖK National Thesis Center.

YÖK's API was redesigned in 2026: searches are now keyword-based against ONE field type at a time (with optional additional keyword slots joined by AND/OR), plus a small set of filter dropdowns (type, language, permission, status, years).

University/institute/department text filters are no longer respected by YÖK and have been removed from this tool. The 'thesis_number' parameter has also been removed since YÖK no longer supports direct lookup by thesis number through this endpoint.

Provide either:

  • 'keyword' (preferred — combine with 'search_field' if you need to restrict the search to a specific field like title or author), or

  • one of the legacy aliases (thesis_title, author_name, advisor_name, subject_headings, index_terms, abstract_text) which auto-set 'search_field'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number of the search results.
keywordNoPrimary search term — what to look for in YÖK theses. E.g. 'yapay zeka', 'machine learning', 'AHMET YILMAZ'. Either this or one of the legacy field-specific parameters (thesis_title, author_name, advisor_name, subject_headings, index_terms, abstract_text) must be provided.
languageNoFilter by thesis language.0
year_endNoEnd year for the search range (e.g. '2025'). '0' = no upper bound.0
keyword_2NoSecond search term (optional). Combined with 'keyword' via 'operator_1'.
keyword_3NoThird search term (optional). Combined with 'keyword_2' via 'operator_2'.
match_typeNoICERSIN = keyword appears anywhere (default). TAM_IFADE = exact phrase match.2
operator_1NoBoolean operator between 'keyword' and 'keyword_2'.and
operator_2NoBoolean operator between 'keyword_2' and 'keyword_3'.and
year_startNoStart year for the search range (e.g. '2020'). '0' = no lower bound.0
author_nameNoDEPRECATED legacy alias. If provided, search_field is set to YAZAR.
index_termsNoDEPRECATED legacy alias. If provided, search_field is set to ANAHTAR_KELIME.
thesis_typeNoFilter by thesis type.0
advisor_nameNoDEPRECATED legacy alias. If provided, search_field is set to DANISMAN.
search_fieldNoWhich field to search the keyword(s) in. TUMU = all fields (default), TEZ_ADI = title, YAZAR = author, DANISMAN = advisor, KONU = subject, ANAHTAR_KELIME = index/keyword terms, OZET = abstract.7
thesis_titleNoDEPRECATED legacy alias. If provided, search_field is set to TEZ_ADI and 'keyword' is filled from this.
abstract_textNoDEPRECATED legacy alias. If provided, search_field is set to OZET.
thesis_statusNoFilter by approval status. Defaults to 'Onaylandı' (approved).3
results_per_pageNoNumber of results to display per page.
subject_headingsNoDEPRECATED legacy alias. If provided, search_field is set to KONU.
permission_statusNoFilter by PDF access permission (İzinli / İzinsiz).0

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
thesesNoList of found theses summaries.
total_pagesNoTotal number of pages available based on results_in_batch and limit_per_page.
current_pageYesThe current page number of the search results.
error_messageNoError message if the search failed or no results were found.
results_in_batchNoNumber of results actually returned in the current HTML batch. YÖK caps this at ~2000 even when total_results_found is larger.
total_results_foundNoTotal number of results found as reported by YÖK.
query_used_parametersNoThe parameters used for this search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations were supplied, but the description discloses important behaviors: the 2026 API redesign, removed thesis_number lookup, legacy aliases auto-setting search_field, and AND/OR combining. It does not mention rate limits or output behavior, but output schema covers result shape.

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?

Well organized with lead rationale, then explicit 'Provide either' bullet structure. Slightly long due to repeated legacy-alias detail, but each sentence adds necessary migration/usage context.

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?

Covers the changed API behavior, required input options, filters, and pagination. Since output schema exists but is not shown here, the description appropriately focuses on invocation semantics rather than return shape.

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 covers all 21 parameters with descriptions; the description adds cross-parameter constraints and preferred usage (keyword vs legacy aliases, operator chaining, removed fields). This raises it above the schema-alone baseline.

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?

Clearly states it searches the YÖK National Thesis Center with keyword-based search and filters. The 'detailed' scope and legacy-alias behavior distinguish it from sibling listing/detail tools.

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?

Provides explicit guidance to prefer 'keyword', combine with 'search_field', and explains legacy aliases and removed parameters. It does not explicitly contrast with sibling search-by-anabilim-dali, but the usage instructions are otherwise strong.

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